sameersbn / sameersbn/docker-gitlab
Error restarting docker after upgrade to 11.8.1
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
I've updated the docker to 11.8.1.
The docker at first start with docker-compose up is ok, but after the restart the docker fails with this error:
Configuring gitlab::timezone...
Configuring gitlab::rack_attack...
Configuring gitlab::ci...
Configuring gitlab::artifacts...
Configuring gitlab::lfs...
Configuring gitlab::uploads...
Configuring gitlab::mattermost...
Configuring gitlab::project_features...
Configuring gitlab::oauth...
Configuring gitlab::ldap...
Configuring gitlab::cron_jobs...
Configuring gitlab::backups...
Configuring gitlab::registry...
Configuring gitlab::pages...
Configuring gitlab-shell...
Configuring nginx...
Configuring nginx::gitlab...
/sbin/entrypoint.sh: line 18: 563 Terminated /usr/bin/supervisord -nc /etc/supervisor/supervisord.conf
Error: The directory named as part of the path /home/git/gitlab/log/gitlab-workhorse.log does not exist. in section 'program:gitlab-workhorse' (file: '/etc/supervisor/conf.d/gitlab-workhorse.conf')
For help, use /usr/bin/supervisord -h
Thanks.
Flavio
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the restart flow with docker-compose up after upgrading to 11.8.1, then inspect /sbin/entrypoint.sh and /etc/supervisor/conf.d/gitlab-workhorse.conf. The reported failure is that /home/git/gitlab/log/gitlab-workhorse.log refers to a missing directory; done means the container restarts successfully without this supervisord error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, shell
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100