Yesterday, I ran into a post talking about cockpit, a web interface to manage server sponsored by Red Hat. I thought that it would have been something good to set up for my Raspberry Pi so I installed it. I then found out that it has a bunch of plugins to expand upon the base features, including a plugin for managing containers managed by podman. That made me switch from docker to podman. Overall, the switch was pretty quick. Arch Linux even has a package that substitutes/symlinks podman on top of docker, so that the transition is seamless.

The only snag I ran into was trying to use podman-compose to run some services stacks. It didn’t really want to run when I had network_mode: service:<name> instances and it wouldn’t network the container correctly. But, I ran into a happy accident that solved the issue. As the networking wasn’t working, I decided to revert back to docker while I figured out how to set up networking through podman-compose. It happened that podman-docker did not uninstall and docker-compose was actually calling podman under the hood, correctly networking the services through the right network interfaces. Long story short, now I have podman running my containers and docker-compose to set up more complex services.

The only thing that I had to update was the wireguard configuration. For whatever reason, it stopped working. I had to replace a %i with the actual wireguard interface name (wg0).

Oh, I also set up a new gitea instance. It’s not like the old one (right now it just mirrors my GitHub repos) but it’s working again.