It’s possible to run Podman as non-root, such that it runs in the context of a standard user. This is pretty good for a number of reasons, but there’s a few steps that need to be done to make this happen.

As I discussed in my post on Jekyll, you can run Jekyll in a container. I’ve since modified this process somewhat due to running into what looks like a 2020 windowing bug with old versions of Ruby.

I’m doing a fair bit of mucking about in Minecraft lately, specifically with All The Mods 3 Remix. One thing that’s a common problem in modded minecraft is maintaining stock of materials.

After a fair bit of mucking about, I think I’ve come up with a fairly modular way to put together a Minecraft server in Podman. Obviously this script makes quite a few assumptions, so you’ll need to make some changes;

Continuing from last post, I’ve also been looking at applying CPU/disk shares and weighting to my various virtual machines to also help regulate load. This is in addition to the per-device IOPS limitations I talked about using virsh blkdeviotune.

As discussed earlier, I’ve switched over to using Jekyll for generating this blog. So far, so good. But what I wanted to do was run the Jekyll serve components in Podman, so I could preview changes without having to have local Ruby installs.