Facebook
Twitter
QWeb Ric
Regular Pleskian
- Server operating system version
- AlmaLinux 9.5
- Plesk version and microupdate number
- 18.0.68 #2
I've spent the weekend experimenting with Docker and various Mastodon, Redis, and PostgreSQL set-ups, but for the life of me can't seem to get a working config. All of the Mastodon via Docker guides seem to be from a few years ago, before Plesk had a Docker extension, and talk about editing yml config files directly and/or running docker-compose, but I'm just trying to use the Docker extension alone.
If I pull the tootsuite/mastodon image through the extension, regardless of the environment variables I set, port mapping, volume mapping, etc, this image just seems to spit out a Tini info page and then exit. I've given up entirely on this image.
If I pull the bitnami/mastodon, bitnami/redis, and bitnami/postgresql images + set up the Redis and PostgreSQL containers and populate the appropriate environment variables within the Mastodon container to connect to them, using the IPs Portainer shows for each, then the Mastodon container appears to connect to the PostgreSQL database and spits out a "Migrating database" line so the bridging and port mapping at least seem to be working, but then just exits after a couple more minutes with no further output. Also despite finding the PostgreSQL database to connect to, the init lines still show "MASTODON_DATABASE_HOST could not be resolved" and "MASTODON_REDIS_HOST could not be resolved" outputs.
Additionally, setting up volume mapping for Redis and PostgreSQL works - I can see files created in the host folders when I do - but setting up for the Mastodon bucket doesn't result in any file dumps, either with the tootsuite/mastodon image or with bitnami/mastodon. Possibly just because the init process isn't getting far enough along to create anything. I'm aware Bitnami containers are non-root but so tried chowning the host directories but neither 991 or 1001 kicks them into life.
Has anybody had better luck with this? I feel like there's no technical reason for Mastodon hosting via Plesk and the Docker extension to not be possible, particularly if people have been running it via Docker outside of Plesk for years?
If I pull the tootsuite/mastodon image through the extension, regardless of the environment variables I set, port mapping, volume mapping, etc, this image just seems to spit out a Tini info page and then exit. I've given up entirely on this image.
If I pull the bitnami/mastodon, bitnami/redis, and bitnami/postgresql images + set up the Redis and PostgreSQL containers and populate the appropriate environment variables within the Mastodon container to connect to them, using the IPs Portainer shows for each, then the Mastodon container appears to connect to the PostgreSQL database and spits out a "Migrating database" line so the bridging and port mapping at least seem to be working, but then just exits after a couple more minutes with no further output. Also despite finding the PostgreSQL database to connect to, the init lines still show "MASTODON_DATABASE_HOST could not be resolved" and "MASTODON_REDIS_HOST could not be resolved" outputs.
Additionally, setting up volume mapping for Redis and PostgreSQL works - I can see files created in the host folders when I do - but setting up for the Mastodon bucket doesn't result in any file dumps, either with the tootsuite/mastodon image or with bitnami/mastodon. Possibly just because the init process isn't getting far enough along to create anything. I'm aware Bitnami containers are non-root but so tried chowning the host directories but neither 991 or 1001 kicks them into life.
Has anybody had better luck with this? I feel like there's no technical reason for Mastodon hosting via Plesk and the Docker extension to not be possible, particularly if people have been running it via Docker outside of Plesk for years?
