Live data from Hacker News

Docker is dead? Podman – an alternative tool?

content.fme.de

11–20 of 183 posts

Re: Docker is dead? Podman – an alternative tool?

#11
Why 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.

Re: Docker is dead? Podman – an alternative tool?

#12

Why 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.

[deleted]

Re: Docker is dead? Podman – an alternative tool?

#14
post #6

Think 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)

Re: Docker is dead? Podman – an alternative tool?

#15
post #6

Think 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…

Just to be clear, privileged containers with CAP_SYS_ADMIN do have additional privileges outside of normal 'containerized' workloads, just having it in a container does not mean that the security side affects are inconsequential.

Re: Docker is dead? Podman – an alternative tool?

#17
post #8

Docker 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.

Re: Docker is dead? Podman – an alternative tool?

#18
NixOS 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 running the container (though I suppose this last bit is supposedly a feature). Why isn't the list of images global to the machine? Perhaps I just don't get it yet.

Re: Docker is dead? Podman – an alternative tool?

#19
post #8

Docker 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.

It has something like a minikube k8s distribution and introduces some compatibility layer for systems without *nix hyper v or wsl

Re: Docker is dead? Podman – an alternative tool?

#20

Why 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?
Post reply on HN