cockpit-podman VS nerdctl

Hey, I have homelab NUC server where I run different services as rootless podman pods and containers running by dedicated users, eg. nextcloud pod running by nextcloud user, gitea by gitea, znc by znc and more. Next step was trying to monitor these services. First trey was using cockpit-podman feature, but in UI I see only containers of my user and rootfull which both was empty. I cannot switch to another user because the're not capable for login to cockpit. Now I'm testing prometheus and podman-exporter which seems ok, but again I see containers only if I run prometheus-podman-exporter service as user who run another podman container (e.g. as nextcloud user). Of course I can run this service parallel as dedicated user with another port and add them as target to prometheus scrape config but from obvious reason I want to avoid that. Is it more gentle way to monitor my pods? I know that those namespaces are one of the main feature of Podman but I don't consider this before my deploys :)

Cockpit has a podman module (cockpit-podman)

Tested podman to replace docker (the cli) on a mac yesterday Most of it works fine. They have an easy way to setup a vm now with `podman machine`: https://podman.io/getting-started/installation#macos

If you want the management GUI, install cockpit: https://github.com/cockpit-project/cockpit-podman

Try podman, you'll be impressed.

What about the docker-cli? colima also ships with a docker-compatible cli to interact with containerd called nerdctl. We can execute the same docker cli commands like:

Using nerdctl: https://github.com/containerd/nerdctl

I'd really disagree that compose files are somehow one-shot, or blindly modified. To the contrary, really, we have them checked in with the source code. Upon deployment to the cluster, the (running) services will be intelligently updated or replaced (in a rolling manner, causing zero downtime). LXC might be more elegant, but I have no idea what simple, file-based format I could use to let engineers describe the environment their app should run in without compose.

I need something that even junior devs can start up with a single command, that can be placed in the VCS along with the code, and that will not require deep Linux knowledge to get running. Open for suggestions here, really.

Now since Kubernetes works off of containerd I'll be taking a different approach on handling container builds by using nerdctl and the buildkit that comes bundled with it. I'll do this on the amd64 control plane node since it's beefier than my Raspberry Pi workers for handling builds and build related services. Go ahead and download and unpack the latest nerdctl release as of writing (make sure to check the release page in case there's a new one):

That's why nerdctl, their cli binary, is so well named.

Well, it is indeed a good option. However, containerd is a good alternative that is growing even among developers. Please see: https://github.com/containerd/nerdctl

Nerdctl/containerd has IPFS support :)

https://github.com/containerd/nerdctl/blob/main/docs/ipfs.md

nerdctl supports IPFS for both image pulling and pushing, including encrypted images and eStargz lazy pulling. For building, the current method is a locally hosted translator so that the traditional pulls can be converted to work over IPFS. They even have docs on running it on k8s node, though if my reading is correct this isn't exactly a cloud native approach (running systemd services on each node...).