Docker upgrade: got stuck

Troubleshooting
1

Fresh docker 7.8.8 install. All good. Upgraded to 8.1. Service unavailable

New install 7.8.8 working well. Changed .env with

MATTERMOST_IMAGE=mattermost-enterprise-edition
MATTERMOST_IMAGE_TAG=8.1

docker compose down
docker compose up -d

now get “SERVICE UNAVAILABLE”
docker logs of running container show continuous repeats of:

{"timestamp":"2023-09-18 10:58:45.299 +02:00","level":"debug","msg":"Worker received a new candidate job.","caller":"resend_invitation_email/worker.go:67","worker":"resend_invitation_email"}
{"timestamp":"2023-09-18 10:59:00.300 +02:00","level":"debug","msg":"Worker received a new candidate job.","caller":"resend_invitation_email/worker.go:67","worker":"resend_invitation_email"}
{"timestamp":"2023-09-18 10:59:02.275 +02:00","level":"debug","msg":"Received HTTP request","caller":"web/handlers.go:163","method":"GET","url":"/api/v4/system/ping","request_id":"izwrqgw4cpgxtezpr8gnap9sue","status_code":"200"}

docker ps shows:

97fa5a337379   mattermost/mattermost-enterprise-edition:8.1   "/entrypoint.sh matt…"   13 minutes ago   Up 13 minutes (healthy)   8065/tcp, 8067/tcp, 8074-8075/tcp, 0.0.0.0:8443->8443/tcp, 0.0.0.0:8443->8443/udp, :::8443->8443/tcp, :::8443->8443/udp   docker-mattermost-1
42f96ab38747   postgres:13-alpine                             "docker-entrypoint.s…"   13 minutes ago   Up 13 minutes             5432/tcp                                                                                                                  docker-postgres-1
2

Got it :slight_smile: I am running the docker behind an hosted Apache2 proxy which routes 80/443 to the 8065 address … needed to expose this ALSO in the docker-compose.yml file.

Not sure I understand how come it did work in the 7.8.8 container though ???

3

Woo hoo! Thanks for following up, Robert. It’s great to hear that you were able to identify the issue and resolve it by exposing the appropriate ports in the docker-compose.yml file. Regarding your question about why it worked in the 7.8.8 container, it’s possible that the previous version had a different configuration or default settings that allowed it to work without explicitly exposing the ports in the docker-compose.yml file? I have to say though, I’m not entirely sure.

If you have any more questions or need further assistance, feel free to ask!

1 Like