Last checked and updated on April 15, 2026What Is New in Podman 3.0
Podman 3.0 is a major release that brings significant enhancements, particularly in Docker compatibility, the new Podman Machine tool for macOS, and core container management improvements. This version marks a substantial step forward in providing a seamless experience for developers and operators moving from Docker.
| Category | Key Changes |
|---|---|
| New Features | Podman Machine for macOS, Docker Compose support, New `podman kube play` command |
| Improvements | Enhanced Docker compatibility (`docker` alias), Improved volume and file handling, Better Windows container support |
| Bug Fixes | Numerous fixes across pods, networking, image handling, and the REST API |
| Deprecations | Deprecation of the `podman run --mac-address` flag |
What's the deal with the new Docker compatibility features?
The core focus of 3.0 is closing the gap with Docker's CLI. You can now use docker as an alias for podman on your system, making the transition almost invisible for existing scripts and muscle memory. Under the hood, Podman translates these commands to its own native logic.
This matters because it removes a major adoption barrier. Teams can point their existing toolchains and scripts at Podman without massive rewrites. In practice, you can set alias docker=podman and most things just work as expected.
How does Podman Machine improve the macOS experience?
Podman Machine is the answer for macOS users, providing a seamless way to manage a Linux VM that hosts your containers. It's a dedicated tool that handles the lifecycle of the VM, making the setup process straightforward.
You can initialize and start a VM with a simple command. This approach isolates the container environment from the host OS, which is the standard pattern for running Linux containers on macOS. It brings the Podman experience on par with other container runtimes on the platform.
$ podman machine init
$ podman machine startCan I finally use Docker Compose with Podman?
Yes, Podman 3.0 introduces native support for Docker Compose. You can now use the podman-compose script to deploy your existing docker-compose.yml files directly.
This is a game-changer for development workflows that rely on Compose. Instead of having to rewrite definitions into Podman pods, you can run them directly. The implementation uses Podman's native core, not the Docker daemon, maintaining the daemonless architecture.
What are the new commands for Kubernetes workflows?
A new podman kube play command has been added to complement the existing podman generate kube. This allows you to take a Kubernetes YAML file and create Podman pods and containers from it directly.
This strengthens the Kubernetes-style workflow within Podman. You can now go from a running container to YAML and back again, which is incredibly useful for testing and development cycles that target Kubernetes but run locally with Podman.
How is volume and file handling better?
Volume management has seen key improvements, including better handling of the --opt device option for mountpoints. File copy operations between the host and containers (podman cp) have also been made more robust.
In practice, this means fewer edge cases and errors when dealing with persistent data. Copying files in and out of containers feels more reliable, which is a common daily task for developers debugging and configuring their applications.
FAQ
How do I set the `docker` alias on my system?
You can create a symbolic link or a shell alias. The simplest method is adding alias docker=podman to your shell's configuration file (e.g., ~/.bashrc or ~/.zshrc). After sourcing the file or opening a new terminal, typing docker will invoke Podman.
Is Podman Machine required for Linux users?
No, Podman Machine is specifically for environments that need to run Linux containers on a non-Linux OS, like macOS or Windows. On a native Linux machine, Podman runs containers directly on the host kernel without the need for a VM.
Does `podman-compose` support all Docker Compose features?
While the goal is full compatibility, the initial implementation in 3.0 might not cover every single advanced feature or option found in a Compose file. It handles the vast majority of common use cases, but complex deployments might require checking the specific documentation for any limitations.
What happens if I use the deprecated `--mac-address` flag?
The flag is still present but will now output a warning message when used, indicating it is deprecated. Your command will still execute, but you should stop using this flag as it will likely be removed in a future major release.
Can I use the new Kubernetes support with Minikube or Kind?
The podman kube play command is for running Kubernetes YAML locally using Podman's own infrastructure, not for interacting with an external cluster. For tools like Minikube or Kind, you would continue to use kubectl to apply configurations to those specific clusters.