> Podman currently only runs stably on Linux-based systems. Under Windows or MacOS it becomes a bit more demanding, although it is possible with detours.
I think this is an area bearing improvement before most dev workflows can switch
Docker is dead? Podman – an alternative tool?
21–30 of 183 posts
Re: Docker is dead? Podman – an alternative tool?
#22Think it is rapidly moving towards being more of a data carrier/format rather than being dead per se. Half the time you're jamming it into some cloud service anyway where you have no idea what GCP/fly/aws is using under the hood to actually run it. Meaning this discussion is more relevant to the self-hosted context. In which case I'd say containerization isn't really security. So in my mind that residual risk of the…
I'm still in the VM all the things camp. Like, containers are neat but VMs have the same cheapness for me - that is deploy some VM per app. Like Docker per app. Many times these days I'm one VM for just one Docker package. (Can you tell VM is my favorite isolation method)
Fargate and Fly are actually both Firecracker VMs, not containers.
Re: Docker is dead? Podman – an alternative tool?
#23Why not both? Since Podman 4.1 came out with full Compose 2.x compatibility, I'm running Podman on Docker's socket, but using Docker's CLI to talk to it, so that I can use the buildx and compose CLI plugins. It works great, Docker's CLI doesn't seem to have any clue that it's talking to not-Docker. I even have VSCode's Docker extension and Remote Containers working this way.
Wow did not know about full compose support going to check it out now.
Re: Docker is dead? Podman – an alternative tool?
#24Earlier quoted context omitted.
I'm still in the VM all the things camp. Like, containers are neat but VMs have the same cheapness for me - that is deploy some VM per app. Like Docker per app. Many times these days I'm one VM for just one Docker package. (Can you tell VM is my favorite isolation method)
Fargate and Fly are actually both Firecracker VMs, not containers.
Yea, super fast boot VMs are a game changer in the container vs VM game.
Re: Docker is dead? Podman – an alternative tool?
#25Docker for Desktop went from being complete garbage to a really nice product. I think Docker folks are heavily focused on providing great local development experiences, which is a niche few other products are covering.
What exactly does Docker for Desktop do? All it seems to me is a slightly annoying non-free GUI application I need to use docker cli from Windows or Mac.
Runs docker in a VM for you, abstracts that away, confuses the hell out of new and old developers alike.
Re: Docker is dead? Podman – an alternative tool?
#26Why not both? Since Podman 4.1 came out with full Compose 2.x compatibility, I'm running Podman on Docker's socket, but using Docker's CLI to talk to it, so that I can use the buildx and compose CLI plugins. It works great, Docker's CLI doesn't seem to have any clue that it's talking to not-Docker. I even have VSCode's Docker extension and Remote Containers working this way.
Is there any config to set up this way or do you literally just run podman on the socket and it just knows what to do?
podman replacing the docker socket
Re: Docker is dead? Podman – an alternative tool?
#27NixOS recently switched the default from docker to podman for containers. I don't know if it's Nix's configuration, or a problem with Podman itself, but it's unusable. The systemd service often hangs, creating networks errors out, the pod concept doesn't work great, requiring tearing down the whole group of containers to change port mappings, and it acts like a completely different system depending on the user runnin…
> Why isn't the list of images global to the machine?
Why would it be? Unless you jump through hoops, your music and photos aren't global to the machine; rootless containers just made containers fit in the traditional unix security model.
Re: Docker is dead? Podman – an alternative tool?
#28This would all be true if podman wasn't a gimped version of docker.
In my experience it is quite the opposite really, a more featureful solution with much more options and safer defaults.
Re: Docker is dead? Podman – an alternative tool?
#29Rootless podman is my first choice for using containers now, it works fantastically well in my experience. It's so much nicer to have all my container related stuff like volumes, configs, the control socket, etc. in my home directory and standard user paths vs. scattered all over the system. Permission issues with bind mounts just totally disappear when you go rootless. It's so much easier and better than the root privileged daemon.
I really wish rootless podman/docker was the default install now. It's still kind of annoying to setup with reading a smattering of old docs and having to think about your distro setup, cgroups settings, etc. It really should just be a "run this install script and you're done".
Re: Docker is dead? Podman – an alternative tool?
#30Have you ever used podman-compose? It's amount of bugs and missing features is bigger than actual features count.