Live data from Hacker News

Podman Desktop Companion GUI – Parity on All Major Operating Systems

iongion.github.io

61–70 of 118 posts

Re: Podman Desktop Companion GUI – Parity on All Major Operating Systems

#61
post #57
post #17

Anyone know if podman has an equivalent to `docker buildx` yet? Right now I use docker a lot to build arm images to deploy on e.g. Raspberry Pis.

I keep hearing that buildx is a next-gen build tool, but I can't find what exactly it does. What features does it add over the classic `docker build` command?

I am also unsure how buildx works, however I do know that the official docker build-and-push action is not compatible with podman (despite the podman-docker pkg), solely because it uses buildx. As well, compared to buildah builds, building with buildx is much faster--at least with default flags for buildah-build-and-push vs docker-build-and-push. I can say that buildx has an additional cache that must be cleared overtime, which might be related to the build speed difference.

Re: Podman Desktop Companion GUI – Parity on All Major Operating Systems

#63

So question from novice in containers, podman vs docker why should i consider switching from docker?

Docker is under a commercial license and if you use it at a company or work you need to now pay $5 a person a month: https://www.docker.com/pricing/ This changed in the last year, previously docker was free to use personally or at non enterprise scale work/office.

From what I read, the "Personal" $0 tier still has "small businesses" listed, and the little info tooltip for Docker Desktop also explicitly mentions "small businesses."

This can be found at the very bottom of that page:

> Docker Desktop can be used for free as part of a Docker Personal subscription for: small companies (fewer than 250 employees AND less than $10 million in annual revenue), personal use, education, and non-commercial open source projects.

Re: Podman Desktop Companion GUI – Parity on All Major Operating Systems

#64
post #12

Earlier quoted context omitted.

A few elements to inform the decision: - Both docker and podman support rootless containers. - Rootless podman setup is easier to achieve from experience and it integrates well enough with systemd. - Docker requires a daemon to run at all times whereas podman doesn't. - A lot of interesting things are going on with podman ("native" gitlab-runner executor in the works, wsl2 support, among other things)

Doesn't Docker already support WSL2? Or is there something different about Podman's WSL2 support which makes it better/different than/from Docker's?

Docker supports wsl2 but I have constant performance issues with it (memory leak, high CPU usage).

Re: Podman Desktop Companion GUI – Parity on All Major Operating Systems

#65
post #45
post #12

Earlier quoted context omitted.

A few elements to inform the decision: - Both docker and podman support rootless containers. - Rootless podman setup is easier to achieve from experience and it integrates well enough with systemd. - Docker requires a daemon to run at all times whereas podman doesn't. - A lot of interesting things are going on with podman ("native" gitlab-runner executor in the works, wsl2 support, among other things)

Where can I find more information about this 'native' gitlab-runner executor?

I'm following this issue:

https://gitlab.com/gitlab-org/gitlab-runner/-/issues/27119

Re: Podman Desktop Companion GUI – Parity on All Major Operating Systems

#66
post #12

Earlier quoted context omitted.

A few elements to inform the decision: - Both docker and podman support rootless containers. - Rootless podman setup is easier to achieve from experience and it integrates well enough with systemd. - Docker requires a daemon to run at all times whereas podman doesn't. - A lot of interesting things are going on with podman ("native" gitlab-runner executor in the works, wsl2 support, among other things)

podman indeed has many interesting features, but those features tend to have interesting bugs and limitations as well.

What got me at first are the limitations around rootless containers, which I wasn't accustomed to. Rootfull docker makes many things (networking, volumes etc.) Fairly easy.

I've found this troubleshooting page quite helpful: https://github.com/containers/podman/blob/main/troubleshooti...

Re: Podman Desktop Companion GUI – Parity on All Major Operating Systems

#67
post #17

Anyone know if podman has an equivalent to `docker buildx` yet? Right now I use docker a lot to build arm images to deploy on e.g. Raspberry Pis.

Somewhat related, do all registries support pushing multi arch builds? DockerHub works, but I can't get it to work with GitHub registries.

I've managed to push amd64/arm64 images to GitHub a while ago, but I was still using Docker proper at the time, so the registry itself should support this.

Re: Podman Desktop Companion GUI – Parity on All Major Operating Systems

#68
post #54

Earlier quoted context omitted.

Yep, docker in wsl2 is great, including GPU support wsl2 mode is super impressive -- none of the overhead of docker on os x

None? How does it manage that, it’s still running in a (Hyper-V) VM? Are there any good docs/blogs that go into detail on how they’ve managed to avoid that overhead? Would be awesome to learn about

For the comparison to os x docker, the biggest slowdown for os x docker is the file system mapping. It basically breaks any reasonable performance chart: look up posts getting into alternatives like mutagen. The slowdown makes using an IO-heavy dev flow like live editing via `npm run watch` relatively unusable: 30X+ slowdowns are normal. There might be high CPU overheads too (I recall we had to tweak seccomp), but when basic IO is so slow, the rest doesn't matter.

In contrast, yes, wsl2 has 5% CPU hits (hyperv, ...),but a sane FS mapping, so the total overhead is imperceptible for a windows dev box.

I was pleasantly surprised to see wsl2 Just Work. Our only issue preventing wsl2 from being the official team rec over native Linux has been wsl2's lack of opencl, and that's just specific to our use of GPUs. As someone whose preferred dev box has been osx for ~20 years, even when at MS, I was biased against Windows for most dev... but no longer.

Re: Podman Desktop Companion GUI – Parity on All Major Operating Systems

#69
post #32
post #30

Is the Podman CLI both command-compatible and flag-compatible with the Docker CLI? If it is, or if there were a command translation layer to transform docker cli stanzas to the podman equivalent, I'd love to dump and forget about docker forever. Please keep pushing Team Podman! Self-respecting nerds everywhere are rooting for (and counting on) you!

It is! At least 99%, in my experience. The one big difference is that Podman is "daemonless", which is actually a huge advantage in a lot of cases. The one downside is that it won't automatically restart your containers if your host machine reboots.

I want to mention the "-userns=keep-id" option of podman, which is a reason enough to use podman rather than docker on a Linux laptop.

Re: Podman Desktop Companion GUI – Parity on All Major Operating Systems

#70
post #51
post #30

Is the Podman CLI both command-compatible and flag-compatible with the Docker CLI? If it is, or if there were a command translation layer to transform docker cli stanzas to the podman equivalent, I'd love to dump and forget about docker forever. Please keep pushing Team Podman! Self-respecting nerds everywhere are rooting for (and counting on) you!

Even better. It”s API compatible with the docker daemon. You can run podman-system-service and get a socket/port that you can point the official Docker CLI or any Docker library at and it will just work (tm).

I’ve run into many issues with tools when moving from docker to podman, mostly because they tried to be smart.

Some tools try to detect whether podman exists on the system or not and change their behaviour accordingly. I couldn’t get docker-compose to work properly either even though I had a socket exposed.

I would much prefer if the podman binary/cli also supported the compose command.

Then there are slight differences such as the registry that is used by default when resolving. Docker defaults to docker.io where podman asks. The same when an image is available in multiple registries.

Post reply on HN