Server

I had to do many things to get adguard-Home running as a container in fedora Server 43. This is how I set it up on Fedora Server 43, so your mileage with say, Tumbleweed might vary. There’s a number of steps that I had to take to get this to work correctly and as a brief overview they were: /etc/sysctl.conf to allow pasta to bind to port 53 Stop systemd-resolvd.service from using port 53 /etc/systemd/resolved.conf.d/no-stub.conf Use loginctl enable-linger run the container as my user-id and not as root: ~/.config/containers/systemd/adguardhome.container All port mappings and container start are to be done in cockpit itself I didn’t necessarily do them in the order above, as I fudged my way through it! Hopefully now you don’t have to! ...

One of the reasons I got myself a home server is so that I can learn about containers. I’ve just got my first one set up, and as this was my first ‘rodeo’ it certainly took a while, but it turned out to be really quite easy in the end. So, here’s how I did it, and just as importantly - also what I learned. podman and quadlet I decided that I wanted to see if I could run a Minecraft server on my home server - because, why not? I’ve never had anything to do with containers before. However, I’m not an expert, but looking through the MicroOS docs I knew that I needed to use podman, which is like Docker, and that it came pre-installed on MicroOS. Later on, I realized that there was another app called quadlets - it’s now deprecated and merged into Podman since version 4.4 - that has really good functionality that I should use. ...