docker-gitlab: after docker-compose restart gitlab exited with error

Hi, After a successful docker-compose up, I’d like to reboot the container. I tried docker-compose down/stop, then I’d like to start it again I received errors like this:

/volume1/docker/gitlab# docker-compose up
Starting gitlab_postgresql_1 ... 
Starting gitlab_redis_1 ... 
Starting gitlab_postgresql_1
Starting gitlab_redis_1 ... done
Creating gitlab_gitlab_1 ... 
Creating gitlab_gitlab_1 ... done
Attaching to gitlab_postgresql_1, gitlab_redis_1, gitlab_gitlab_1
postgresql_1  | WARNING: no logs are available with the 'db' log driver
redis_1       | WARNING: no logs are available with the 'db' log driver
gitlab_1      | WARNING: no logs are available with the 'db' log driver
gitlab_gitlab_1 exited with code 143
gitlab_1      | WARNING: no logs are available with the 'db' log driver
gitlab_gitlab_1 exited with code 143
......

I watched the log and the last unusual log is: /sbin/entrypoint.sh: line 22: 558 Terminated /usr/bin/supervisord -nc /etc/supervisor/supervisord.conf

Don’t understand the meaning. My yml file is just the standard info and the first up works well.

Could someone help me with this issue? Thank you so much.

About this issue

Original URL
State: closed
Created 6 years ago
Reactions: 2
Comments: 34 (5 by maintainers)

Most upvoted comments

I’m getting a similar error too after an upgrade

mysql: [Warning] Using a password on the command line interface can be insecure.
/sbin/entrypoint.sh: line 22:   657 Terminated              /usr/bin/supervisord -nc /etc/supervisor/supervisord.conf

adamlc on Jun 4, 2018

Ok @flashermaster, I think that now, if you try to start in 10.8.1, it will fail because your data is already in 10.8.3. But 10.8.3 will bootloop as we saw in this issue.

So now, mount a custom entrypoint.sh from your host on path /sbin/entrypoint.sh (like --volume /your/host/path/entrypoint.sh:/sbin/entrypoint.sh), with the content of the script as in the repo sources (entrypoint.sh in on the root of sameersbn/docker-gitlab). Comment lines 18-23, and restart the docker in version 10.8.3. Do not forget chmod +x on entrypoint.sh

For me it worked. Also for @adamlc with a slightly different approach (he modified entrypoint.sh and built his own docker image).

For everyone, it is a working temporary solution, until the repo sources are fixed and a new image is deployed. But it skips database migration, so you should already be on a 10.8.X gitlab version to avoid weird issues.

adferrand on Jun 4, 2018

@derphilipp I’m not upgrading from former version to 10.8.3. I’ve just made a clean installation and a single reboot try. TOT

flashermaster on Jun 4, 2018