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.

In my last post, I talked about how one of my KVM VMs was inflicting very high disk utilization on me. However, there’s some more things about this that has come to light.

When I was trying to do some stuff on my home server this morning, I noticed that performance was absolutely awful. A quick examination of the server with top revealed that the server was getting wrecked by extremely high I/O wait.

I recently put Podman on my KVM hypervisor, so I had a way of running containers alongside full KVM virtual machines. Anyway, I ran into quite the gotcha. Sometimes the Podman container storage doesn’t get unmounted fully when you destroy a container. And I found out why.