Chris
@Gargron Because the docker-compose.yml doesn't specify a tag for the mastodon image, doesn't that mean it always uses the :latest tag? Wouldn't that then cause issues as the "latest" docker tag could be ahead of the latest stable git tag (e.g. tags/v.1.3.3)? #mastodev
May 6, 2017 at 9:33pmWeb
Show threadEugen RochkoMay 6, 2017
@chris You're right. But the docker-compose builds whatever's in your source rather than pulling down a static image
Show threadChrisMay 6, 2017
@Gargron I see, but the gargron/mastodon:latest image does get pulled when running "docker-compose pull". So when running "docker-compose up", does it end up using the image built from source or the image pulled from the hub?
Show threadEugen RochkoMay 6, 2017
@chris I don't know. You're supposed to docker-compose build anyway
Show threadChrisMay 6, 2017

@Gargron Got it, that makes sense. Most of the "running mastodon" guides I read said to run "pull" as well (probably to get the Redis and Postgres images, but I think those would be pulled on-demand when calling "up" anyways).

I think I hit an issue where it pulled and used the :latest image and that didn't match up with the assets from the v1.3.2 source I was on. I'll just clear images, build from source, and hope that works :)