Live data from Hacker News

Podman Desktop Companion GUI – Parity on All Major Operating Systems

iongion.github.io

111–118 of 118 posts

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

#111
post #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.

That’s … debatable.

More importantly, however, working on : OSes frequently is rare. The developer of the app does it. I, as the user, dominantly use a single OS and want apps to be standard for that OS…

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

#113
post #95
post #65

Earlier quoted context omitted.

I'm following this issue: https://gitlab.com/gitlab-org/gitlab-runner/-/issues/27119

thanks!

Npb. It's also listed on the upcomming release page apparently

https://about.gitlab.com/upcoming-releases/

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

#114
post #32

Earlier quoted context omitted.

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.

The biggest drawback for me is that podman cannot build containers.

Huh? I use `podman build` all the time. Sure, it uses `buildah` in the backend, but does that really matter?

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

#115

Earlier quoted context omitted.

For that Podman provides a nifty little trick: `podman generate systemd`[0] which allows you to generate systemd unit files for your pods and/or containers. Once generated and enabled, your pods/containers act as systemd services that can be started, stopped etc. [0]: https://docs.podman.io/en/latest/markdown/podman-generate-sy...

This is no longer necessary as of Podman 3.3 or so--there's a single Podman systemd unit that will launch all containers that have restart=always.

That's awesome, I didn't know about that.

Looks like the service is called podman-restart.service on my system.

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

#117

Earlier quoted context omitted.

The biggest drawback for me is that podman cannot build containers.

Huh? I use `podman build` all the time. Sure, it uses `buildah` in the backend, but does that really matter?

On Mac OS at least there is a bunch of hoops you have to jump through for build to work at all. If I recall you needed virtualbox installed (which I don't want). With docker it just works, you install docker you can run docker build, no extra troubleshooting, or hacky workarounds, just so you can use basic functionality.

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

#118
post #32

Earlier quoted context omitted.

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.

The "podman.service" systemd unit takes care of restarting containers that were marked so.

correction: podman-restart.service
Post reply on HN