i updated my mastodon installation the
other day and it looked like everything went swimmingly. but, i discovered
that they’d changed the structure of the docker containers. this was evident if
i was using the docker-compose.yml that was in the repo and just blithely
using that. but, durrr, i’m not.
this seemed to chug along for a while with little/no apparent ill effects, but
i restarted the containers the other day for something else and lo, the
mastodon-streaming container was unhappy.
note to self, i need to make sure that i’m carefully tracking the container packaging when doing upgrades. there seem to be some subtle elements in the upgrade process that i’ve missed in the release and/or upgrade notes.
at some point, i think this is veering into the realm of, “i should not be hosting this”.
meta
- tags: mastodon, docker
- location: minneapolis, mn
- weather: ⛅️ (Partly cloudy) +23°F(+15°F)