Live data from Hacker News

Podman Desktop Companion GUI – Parity on All Major Operating Systems

iongion.github.io

51–60 of 118 posts

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

#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).

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

#52

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

It's possible to run podman in podman in podman in …, which is nice if you containerize the build system but don't want to pack everything into one large image nor want to divide it into stages called by some main script on the host.

Some extra args needed, though:

  podman run -ti --rm --security-opt seccomp=unconfined --security-opt label=disable --cap-add SYS_ADMIN --env STORAGE_DRIVER=vfs quay.io/podman/stable sh -c 'podman run -ti --rm --security-opt seccomp=unconfined --security-opt label=disable --cap-add SYS_ADMIN --env STORAGE_DRIVER=vfs quay.io/podman/stable sh -c "podman run --rm hello-world"'

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

#53
Seems like a pretty nice Docker-desktop-ish GUI to me.

One remark:

> Application looks the same everywhere, no mental mapping!

That depends on your perspective. If you are on one OS and this non-natve-looking app comes along, you have to mentally map it for your OS so it's none-nativeness requires mapping to the OS-nativeness.

If you, on the other hand, only work "in" this application and just take it with you regardless of the OS, then you would indeed not need to mentally map the application itself. But I doubt this application is used that way in isolation.

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

#54

Earlier quoted context omitted.

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?

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

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

#55
post #26

Earlier quoted context omitted.

Isn't that only docker desktop? AFAIK docker cli and docker daemon are still free.

Yeah, but there's no release of docker daemon for mac or windows. You have to run a linux VM and install and use it there. Docker desktop basically wraps that VM process up into a little gui app. If you're willing to do it yourself then yeah a simple virtualbox VM can run docker without issues or license fees.

I guess it’s time to go back to the old boot2docker xhyve setup I used to have!

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

#56

Earlier quoted context omitted.

The main use case right now is that your company won't spring for a docker desktop license (and you work in a windows/mac shop). It works well enough for single docker images, but I've never gotten it to work well with a complicated docker-compose set-up (I haven't tried in a couple months though, so go check the docs before you write it off).

The macOS Docker Desktop app (I haven’t experienced other versions) is free and works fine. The paid upgrade is only required for certain features that I would imagine many teams don’t need. My complaint with it is that I’d prefer if there was a 100% feature-parity CLI interface so it could run in the background, and that it should be open source. To have a low-level developer tool that’s required to be in my menubar…

It works fine if you're working solo, but companies have to pay for it.

> To have a low-level developer tool that’s required to be in my menubar and administered through a closed-source GUI is IMHO an insane departure from web software development norms.

Yeah, this is why I mentioned the mac/windows shop part. Desktop is only required on mac/windows. On linux, it's just the cli, which works just fine (it's also free).

Docker desktop works pretty well, and I'm not saying they don't deserve the money, but I'm not going to spend my own money to do enterprise work, so I have to investigate alternatives (minikube and podman worked the best, in my experience).

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

#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?

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

#59
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 use it to build x86 images on my M1 MacBook

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

#60

Seems like a pretty nice Docker-desktop-ish GUI to me. One remark: > Application looks the same everywhere, no mental mapping! That depends on your perspective. If you are on one OS and this non-natve-looking app comes along, you have to mentally map it for your OS so it's none-nativeness requires mapping to the OS-nativeness. If you, on the other hand, only work "in" this application and just take it with you regard…

Mapping different behavior between operating systems is much harder than mapping between native and non-native apps.
Post reply on HN