It seems that with the newest version of podman container names are no
longer added as hostnames, meaning that any attempt to resolve
hostnames with the current config will fail. `localhost` is probably
more robust anyway, so we switch to that.
The bug manifests as broken services because nextcloud/gitea cannot
resolve their databases and nextcloud fails to resolve the php
server. To fix this a running system, the gitea and nextcloud database
configurations will need to be hand-edited, since those values are
only set on initialization, and not updated when changed later.
Yes, they completely changed the config format and didn't take into
account the user's changes.
I guess I shouldn't be expecting much from minecraft mod authors, but
damn.
If localhost is specified in the proxyPass url, nginx will happily
resolve IPv6 addresses, even if the upstream doesn't support them.
This can result in connection issues, especially with containers that
don't support IPv6.
Podman pods make this obsolete; though we need to explicitly set
slirp4netns, otherwise podman will not create private network
namespaces for the pods.
In a nutshell:
- Apotheosis
- Don't clutter the world with super tall reed
- Don't ruin spawners - it's nice to build buildings in more
locations
- Ice and fire
- *Really* tone down the griefing and amount of spawns
- Iron furnaces
- *Hopefully* disable the annoying update chat messages
- Quark
- Disable matrix enchanting so that apotheosis works
This removes all existing services as well, in preparation of moving
them to `podman`. These are easier to update to
virtualisation.oci-containers while retaining the "networks" through
pods.
Tristan Daniël Maat