←back to thread

I ditched Docker for Podman

(codesmash.dev)
1101 points codesmash | 7 comments | 05 Sep 25 11:56 UTC | HN request time: 0.238s | source | bottom
Show context
awoimbee ◴[05 Sep 25 15:10 UTC] No.45139493[source]▶
The main issue is podman support on Ubuntu. Ubuntu ships outdated podman versions that don't work out of the box. So I use podman v5, GitHub actions uses podman v3, and my coworkers on Ubuntu use docker. So now my script must work with old podman, recent podman and docker
replies(9): >>45139613 #>>45139704 #>>45139722 #>>45139762 #>>45141829 #>>45142372 #>>45146121 #>>45146243 #>>45149875 #
rsyring ◴[05 Sep 25 15:28 UTC] No.45139704[source]▶
Additionally, there aren't even any trusted repos out there building/publishing a .deb for it. The ones that I could find when I searched last were all outdated or indicated they were not going to keep moving forward.

I could get over this. But, IMO, it lends itself to asking the "why" question. Why wouldn't Podman make installing it easier? And the only thing that makes sense to me is that RedHat doesn't want their dev effort supporting their competitor's products.

That's a perfectly reasonable stance, they owe me nothing. But, it does make me feel that anything not in the RH ecosystem is going to be treated as a second-class citizen. That concerns me more than having to build my own debs.

replies(4): >>45139838 #>>45139861 #>>45143260 #>>45145770 #
1. gucci-on-fleek ◴[05 Sep 25 20:30 UTC] No.45143260[source]▶
They publish statically-linked binaries on GitHub [0], so to install it, you just need to download and unpack a single file. But you don't get any automatic updates like you would if they provided an apt repository.

[0]: https://github.com/containers/podman/releases

replies(3): >>45143542 #>>45144262 #>>45149605 #
2. rsyring ◴[05 Sep 25 21:00 UTC] No.45143542[source]▶
Wow! I can't believe I missed that. Thanks.
replies(1): >>45159655 #
3. Eduard ◴[05 Sep 25 22:12 UTC] No.45144262[source]▶
how come there is no podman Linux installer?
replies(2): >>45144368 #>>45146870 #
4. gucci-on-fleek ◴[05 Sep 25 22:24 UTC] No.45144368[source]▶
Well all the downstream distros have their own installers (apt, dnf, pacman, etc.). If you're compiling from source, then "make install" [0] should work as expected, and if you're downloading the pre-built binaries from GitHub [1], you just need to copy a single statically-linked binary into "/usr/local/bin".

[0]: https://github.com/containers/podman/blob/c8183c50/Makefile#...

[1]: https://github.com/containers/podman/releases

5. xylophile ◴[06 Sep 25 05:31 UTC] No.45146870[source]▶
You mean curl?
6. throwaway127482 ◴[06 Sep 25 14:32 UTC] No.45149605[source]▶
Aren't the statically linked binaries just the remote client? i.e. they can't run containers on their own, right?

In the past I think I wound up using https://github.com/mgoltzsche/podman-static because I could not get those podman static binaries to work

7. rsyring ◴[07 Sep 25 16:30 UTC] No.45159655[source]▶
Apparently, I didn't miss anything after all. :(

See sibling comment above about them being just remote binaries.