It was interesting getting Mastodon up and running on AlmaLinux 9.

The CentOS 9 derivatives boot amazingly fast. At least half of my boot time to shell is waiting for grub! That's awesome for reducing the overhead of maintenance.

I ended up using Docker, which probably makes it take a few seconds longer to boot than if I just ran it all from source, but means I can manage all the services separately. It definitely makes tootctl take longer to run.

I have raw notes of everything I did, which I do intend to edit into a blog post and publish. But probably half the wasted time was from not knowing that docker "internal" networks do not work with firewalld: https://github.com/firewalld/firewalld/issues/844
docker: firewalld 1.0.0-1.1 breaks inter-container networking · Issue #844 · firewalld/firewalld

What happened: Version 1.0.0-1.1 of firewalld breaks inter-container networking, at least for Mastodon's docker-compose.yml. Container mastodon_streaming_1 shows these errors repeatedly while tryin...

GitHub
@mcdanlj interesting that Docker would have a firewall which mingles inside the instance networking. I can see it controlling container-2-container networking but not container internal networking.
@dougl It's intra-container (container-to-container) networking that is the issue — I'm running seven docker containers that need to talk to each other in certain ways, and while Docker now works with firewalld in general, that support doesn't extend to networks that are set as internal.