June 7, 2026
VM drama: now you see me
Podman 6: machine usability improvements
Podman tries to make its virtual machines less confusing, while commenters ask why the news feels late
TLDR: Podman 6 makes its built-in virtual machines easier to find and control, fixing a problem where users could create one and then be told it didn't exist. Commenters were split between relief at the cleanup, confusion over the delayed release timing, and skepticism that this feature matters much anyway.
Podman 6 is rolling out a cleanup that sounds small but hit a very real pain point: people could create a virtual machine in one part of the app, then jump to the command line and be told that machine basically didn't exist. In plain English, Podman used to split its machines into separate hidden buckets, and users had to know which bucket they were in. Now Podman 6 says: enough. It will show all machines by default and let people start or stop them by name without playing a guessing game.
But in the comments, the real drama wasn't just about the fix — it was about the timing. One of the loudest reactions was confusion over why this announcement was being shared at all, with one commenter pointing to a release delay post and basically asking, "Uh, isn't this old news now?" That gave the whole thread a slightly chaotic, "did we just time-travel?" energy.
Then came the practical crowd. One user said they love Podman but aren't sold on this machine feature in the first place, arguing that if they want full virtual computers, they already use traditional virtual machine tools, and if they want container-style workflows, they just use containers. Translation: nice fix, maybe, but some people are still side-eyeing the whole idea. So while Podman is trying to make life simpler, the comments reveal a classic tech community split: finally fixing a confusing mess versus do we even need this feature at all?
Key Points
- •Podman 5 limited CLI machine awareness to the current default provider, even when machines existed under other supported providers.
- •In Podman 5, users could list machines across providers with `podman machine ls --all-providers`, but they could not reliably manage non-default-provider machines by name through the CLI.
- •Podman 6 updates machine commands such as `start`, `stop`, and `rm` so they work by machine name regardless of provider.
- •Podman 6 removes the `--all-providers` flag because listing machines across all supported providers becomes the default behavior.
- •Podman 6 adds a `--provider` option to `podman machine init`, allowing users to create a machine directly with a non-default provider.