DietPi-Software | Podman

[isarrider]

has anybody looked in podman on DietPi so far?
it is on my plan to look into it...

[Joulinar]

not that I'm aware of.

[MichaIng]

Adding the GitHub link: https://github.com/containers/podman

[queeup]

Personally I prefer podman.

[isarrider]

from many POVs, podman is superior...
If I find time, Ill investigate a bit more
and post my findings here...

[Joulinar]

what system you are running? Because on my R5S, it just requires podman as well as dbus to be installed only. No need to manage the cgroupv2 error. I guess it's related to kernel version.

[radekbenkel]

@Joulinar sorry, forgot to mention it above :)

 ─────────────────────────────────────────────────────
 DietPi v8.10.2 : 18:39 - Mon 10/24/22
 ─────────────────────────────────────────────────────
 - Device model : RPi 3 Model B (aarch64)
 - CPU temp : 36 °C / 96 °F : Cool runnings
 ─────────────────────────────────────────────────────
 
 $ uname -a 
 Linux DietPi 5.15.61-v8+ #1579 SMP PREEMPT Fri Aug 26 11:16:44 BST 2022 aarch64 GNU/Linux

EDIT: tried on VirtualBox's VM and got similar errors, cgroupv2 and newuidmap missing.

Maybe in your case other packages added what's required and you can use cgroupManager: systemd instead of cgroupManager: cgroupfs like in my case (based on podman info output) 🤔

[Joulinar]

ok I tested on the same device and it's working ootb

apt install podman dbus
systemctl enable dbus
systemctl start dbus
podman run -dt -p 8080:80/tcp docker.io/library/httpd

and podman ps returns following

root@DietPi:~# podman ps
CONTAINER ID  IMAGE                           COMMAND           CREATED             STATUS                 PORTS                 NAMES
dc634e1cc46d  docker.io/library/httpd:latest  httpd-foreground  About a minute ago  Up About a minute ago  0.0.0.0:8080->80/tcp  jovial_edison
root@DietPi:~#

[radekbenkel]

@Joulinar ok, now it hit me with idea why we have different behavior.

From your examples: root@DietPi:~# podman ps ... root@DietPi ... root. I replicated your instructions as a root (on x86 VM) and indeed everything worked (with cgroupManager ended up being systemd).

My instructions were from a POV of non-root user, as one of the selling points of podman is ability to run rootless containers. My assumption is that's why I needed uidmap (for UID mapping) and slirp4netns (from package description: "User-mode networking for unprivileged network namespaces").

htop output for both cases seem to confirm my assumptions:

• as dietpi:

• as root:

Does it make sense? (again, my Linux-fu is far from being top-notch :)

[Joulinar]

most probably you are right on your assumption with the rootless user setup https://github.com/containers/podman/blob/main/docs/tutorials/rootless_tutorial.md