container

You can execute Docker and Podman commands through a unified engine interface that abstracts Build, Run, Remove, and ImageExists operations. This container engine uses BaseCLIEngine for shared CLI construction to reduce duplication across runtimes.

Yes, Podman works with the same container engine abstraction as Docker in Linux environments. The unified interface coordinates cross-runtime integration, ensuring consistent command execution and path handling across both runtimes.

A SandboxAwareEngine wrapper is a container runtime integration layer that enables Flatpak and Snap sandbox compatibility. It wraps the engine to ensure safe, sandbox-wrapped execution with robust error handling when operating within restricted Linux environments.

To normalize paths and prevent traversal issues during container testing, the engine applies Linux-focused guidance on container support and path handling. This ensures predictable behavior and safe execution across Docker and Podman workflows.

Container engine logic duplicates across different runtimes due to fragmented tooling between Docker and Podman. A shared BaseCLIEngine resolves this by providing shared base logic and a consistent interface for cross-runtime integration.

The best way to start testing container engine abstraction is to instantiate the container engine and verify basic Run and Build flows. Select your preferred backend, either Docker or Podman, to validate the unified interface operations.