sameersbn / sameersbn/docker-gitlab
Can't start container
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
docker-compose.yml
version: "2"
services:
mysql:
image: sameersbn/mysql:latest
environment:
- DB_USER=gitlab
- DB_PASS=
- DB_NAME=gitlabhq_production
volumes:
- mysql-data:/var/lib/mysql
gitlab:
image: sameersbn/gitlab:8.8.1
links:
- redis:redisio
- mysql:mysql
volumes:
- gitlab_data:/home/git/gitlab
ports:
- "10080:80"
- "10022:22"
environment:
- DEBUG=true
- AWS_BACKUP_ACCESS_KEY_ID=
- AWS_BACKUP_SECRET_ACCESS_KEY=
- AWS_BACKUP_BUCKET=
- AWS_BACKUPS=true
- AWS_BACKUP_REGION=eu-west-1
- GITLAB_SECRETS_SECRET_KEY_BASE=
- GITLAB_SECRETS_DB_KEY_BASE=
- GITLAB_SECRETS_OTP_KEY_BASE=
- GITLAB_CI_SECRETS_SESSION_KEY_BASE=
- DB_TYPE=mysql
- DB_HOST=mysql
- DB_USER=gitlab
- DB_PASS=
- REDIS_HOST=redisio
- GITLAB_EMAIL=
- GITLAB_HOST=
- GITLAB_PORT=10080
- GITLAB_SSH_HOST=
- GITLAB_SSH_PORT=10022
- GITLAB_BACKUPS=daily
- SMTP_ENABLED=true
- SMTP_DOMAIN=
- SMTP_HOST=
- SMTP_PORT=
- SMTP_USER=
- SMTP_PASS=
- IMAP_ENABLED=true
- IMAP_HOST=
- IMAP_USER=
- IMAP_PASS=yed6mo5ohJ
- OAUTH_GITHUB_API_KEY=
- OAUTH_GITHUB_APP_SECRET=
redis:
image: sameersbn/redis:latest
volumes:
mysql-data:
external:
name: gitlab_mysql
gitlab_data:
external:
name: gitlab_data
docker logs container
- sed -i '/{{NGINX_HSTS_MAXAGE}}/d' /etc/nginx/sites-enabled/gitlab
- nginx_configure_gitlab_ipv6
- [[ ! -f /proc/net/if_inet6 ]]
- nginx_configure_gitlab_ci
- [[ -n '' ]]
- case ${1} in
- migrate_database
- case ${DB_ADAPTER} in
- QUERY='SELECT count() FROM information_schema.tables WHERE table_schema = '''gitlabhq_production''';'
++ mysql -h mysql -P 3306 -u gitlab -psecretpassword -ss -e 'SELECT count() FROM information_schema.tables WHERE table_schema = '''gitlabhq_production''';' - COUNT=64
- CACHE_VERSION=
- [[ -f /home/git/data/tmp/VERSION ]]
- [[ 8.8.1 != '' ]]
- [[ -n '' ]]
++ vercmp 8.8.1 8.0.0
++ expr '(' 8.8.1 : '([^.])' ')' - '(' 8.0.0 : '([^.])' ')' '|' '(' 8.8.1.0 : '[^.][.]([^.])' ')' - '(' 8.0.0.0 : '[^.][.]([^.])' ')' '|' '(' 8.8.1.0.0 : '[^.][.][^.][.]([^.])' ')' - '(' 8.0.0.0.0 : '[^.][.][^.][.]([^.])' ')' '|' '(' 8.8.1.0.0.0 : '[^.][.][^.][.][^.][.]([^.])' ')' - '(' 8.0.0.0.0.0 : '[^.][.][^.][.][^.][.]([^.])' ')' - [[ 8 -gt 0 ]]
- [[ -n '' ]]
- echo 'Migrating database...'
- exec_as_git bundle exec rake db:migrate
Migrating database...
++ whoami - [[ root == git ]]
- sudo -HEu git bundle exec rake db:migrate
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
Start with docker-compose.yml and the supplied docker logs output, reproducing the failure through the database migration step after COUNT=64. Trace the db:migrate entry point and its MySQL connection, then verify that the compose deployment completes startup without stopping there.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, mysql, shell
- Domain
- databases, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100