Inaccuracies in docker mastodon guide #591
Comments
|
+1. I've run into all of the above confusions myself trying to work from the docker-compose guide. In addition, you'll run into if you follow the directions as written. |
|
@wxcafe i dont use docker |
|
ah. Me neither lol |
|
Who is someone who deploys mastodon with docker? I'd like to deploy it this way myself and I'd like to help out with improving the documentation for it if I can. |
|
Another issue that I'm running into, when running |
|
@neunenak I just finished bringing up my own instance using docker-compose the other day, and ran into the same thing. It throws a warning that it'll delete any extant database if you choose to re-initialize, but it seems the script can't actually do that. ETA: That said, if the database is OK, that error is benign. My instance came up fine without needing to start over. |
As discussed in mastodon#591, docker will refuse to run the `mastodon:setup` step without some configuration file present.
|
We're still running into these problems as well with v2.3.3 on prebuilt images doing a manual We are using a bought cert rather than Let's encrypt. Browser shows a 502 Bad Gateway and the error logs are giving this.
Are the Mastodon systemd Service Files part of the deployment guide required for a docker install? it isn't clear. |
* Adding copy config step As discussed in #591, docker will refuse to run the `mastodon:setup` step without some configuration file present. * The secret generation part of docker installation process As noticed in #6883, you need to generate the keys manually. * Setting correct file owner is important even in the prebuilt-image case ... as evidenced by issue #6911 * This step should not be necessary -- let's fix the installation instead
|
Were all issues resolved with the commit? |
* Adding copy config step As discussed in mastodon#591, docker will refuse to run the `mastodon:setup` step without some configuration file present. * The secret generation part of docker installation process As noticed in #6883, you need to generate the keys manually. * Setting correct file owner is important even in the prebuilt-image case ... as evidenced by issue #6911 * This step should not be necessary -- let's fix the installation instead
I'm new to Mastodon and trying to follow along with https://github.com/tootsuite/documentation/blob/master/Running-Mastodon/Docker-Guide.md
Unfortunately, it seems like some of this documentation is incorrect (possibly out of date?) and I've been having trouble getting a working mastodon instance running by following it.
Some of the inconsistencies I've noticed are:
-nothing in that documentation mentions that the .env.production file needs to exist before
docker-compose buildwill even run. I ended up renaming the default .env.production.sample file to .env.production to make the image happy, but I'm not sure why the build step is even checking for this-if I'm using a prebuilt image from docker Hub rather than compiling from source, does
docker-compose buildeven do anything? it seems like it doesn't-when I run
docker-compose run --rm web rake mastodon:setup, it's not clear to me how the .env.production file that this says it saves relates to the .env.production file that exists outside of docker, in the top-level directory of the cloned repo. When I actually rundocker-compose uplater, which .env.production will it look for?-finally, it's not clear from the documentation what steps in the Production guide (https://github.com/tootsuite/documentation/blob/master/Running-Mastodon/Production-guide.md) are and are not necessary if running mastodon from docker
The text was updated successfully, but these errors were encountered: