When upgrading from version 13.12.11 to version 14.0.12, background migrations does not start.
The environment is running on AWSEC2 with docker-compose.
The docker-compose.yml is as follows
version: “3”
services:
gitlab:
image: “gitlab/gitlab-ce:13.12.11-ce.0”
restart: always
hostname: “xxxxxxxxxxxxxxxxxx”
links:
- postgresql:postgresql
- redis:redis
depends_on:
- redis
- postgresql
environment:
GITLAB_ROOT_PASSWORD: “xxxxxxxxxxxxxxxxxx”
GITLAB_OMNIBUS_CONFIG: |
postgresql[‘enable’] = false
gitlab_rails[‘db_username’] = “xxxxxx”
gitlab_rails[‘db_password’] = “xxxxxx”
gitlab_rails[‘db_host’] = “postgresql”
gitlab_rails[‘db_port’] = “5432”
gitlab_rails[‘db_database’] = “xxxxx”
gitlab_rails[‘db_adapter’] = ‘postgresql’
gitlab_rails[‘db_encoding’] = ‘utf8’
gitlab_rails[‘gitlab_host’] = ENV[“HOST_NAME”]
gitlab_rails[‘gitlab_email_enabled’] = true
gitlab_rails[‘gitlab_email_from’] = ‘xxx@xxxx.xx’
gitlab_rails[‘gitlab_email_reply_to’] = ‘xxx@xxxx.xx’
gitlab_rails[‘gitlab_email_display_name’] = ‘xxx@xxxx.xx’
gitlab_rails[‘smtp_enable’] = true
gitlab_rails[‘smtp_address’] = “email-smtp.ap-northeast-1.amazonaws.com”
gitlab_rails[‘smtp_port’] = 587
gitlab_rails[‘smtp_user_name’] = “xxxxxxxxxxxxxxxxx”
gitlab_rails[‘smtp_password’] = ‘xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx’
gitlab_rails[‘smtp_domain’] = ‘xxxx.xx’
gitlab_rails[‘smtp_authentication’] = “login”
gitlab_rails[‘smtp_enable_starttls_auto’] = true
gitlab_rails[‘db_encoding’] = ‘utf8’
gitlab_rails[‘auto_migrate’] = true
redis[‘enable’] = false
gitlab_rails[‘redis_host’] = ‘redis’
gitlab_rails[‘redis_port’] = ‘6379’
gitlab_rails[‘gitlab_shell_ssh_port’] = 8122
gitlab_rails[‘redis_host’] = ‘redis’
external_url ENV[“EXTERNAL_URL”]
external_url
nginx[‘listen_https’] = false # change
nginx[‘enable’] = true
nginx[‘listen_port’] = 80 # add
logging[‘logrotate_frequency’] = “weekly”
logging[‘logrotate_maxsize’] = 50
logging[‘logrotate_rotate’] = 10
logging[‘logrotate_compress’] = “compress”
logging[‘logrotate_method’] = “copytruncate”
ports:
- “80:80” # add
- “8122:22”
# the following are hints on what volumes to mount if you want to persist data
volumes:
- /share/data0/gitlab/config:/etc/gitlab:rw
- /share/data0/gitlab/logs:/var/log/gitlab:rw
- /share/data0/gitlab/data:/var/opt/gitlab:rw
- /share/data0/gitlab/ssl:/etc/ssl/certs/gitlab:ro
networks:
- default
logging:
driver: “json-file”
options:
max-size: “1m”
max-file: “3”
postgresql:
restart: always
image: postgres:12.9-alpine
environment:
- POSTGRES_USER=xxxxx
- POSTGRES_PASSWORD=xxxxx
- POSTGRES_DB=xxxxx
volumes:
- /share/data0/postgresql/data:/var/lib/postgresql/data/
networks:
- default
ports:
- “5432:5432”
redis:
restart: always
image: redis:5.0-alpine
networks:
- default
networks:
default:
driver: bridge
ipam:
driver: default
config:
- subnet: 10.50.255.0/24
If there is an existing file under /share/data0/, background migrations will not start, but if there is no existing file, it will start.
Is there an existing configuration somewhere that prevents background migrations from starting?
If so, what do I need to change to get background migrations to start?