sameersbn / sameersbn/docker-gitlab

backup not generated automatically

Open
#538 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

wontfix
Dominant language
Shell
Stars
8.1k
Forks
2.1k
Avg merge
17h 47m
Merged PRs (30d)
7

Description

I am running gitlab docker and its working fine. but backup tar is not generated.
below is my command
sudo docker run --restart=always --name gitlab_8_0_5_1_cm2-test -d --env 'TZ=Asia/Kolkata' --env 'GITLAB_HOST=git' --env "USERMAP_UID=$(id -u git)" --env "USERMAP_GID=$(id -g git)" --env 'REDIS_HOST=redis-host' --env 'REDIS_PORT=6379' --env 'NGINX_WORKERS=8' --env 'UNICORN_WORKERS=16' --env 'DB_TYPE=mysql' --env 'GITLAB_BACKUPS=daily' --env 'GITLAB_BACKUP_TIME=10:00' --env 'GITLAB_BACKUP_DIR=/home/git/data/backups' --env 'GITLAB_EMAIL=git@gmail.com' --env 'SMTP_ENABLED=true' --env 'SMTP_HOST=smtp' --env 'SMTP_PORT=25' --volume /home/git//gitlab:/home/git/data -v /home/git//gitlab/logs:/var/log/gitlab/gitlab -v /home/git/gitlab/hooks:/home/git/gitlab-shell/hooks -p 2023:22 -p 8081:80 --env 'DB_TYPE=mysql' --env 'DB_HOST=mysql-host' --env 'DB_NAME=gitlabhq_production' --env 'DB_USER=git' --env 'DB_PASS=mysqlgitpass' --env 'DB_POOL=50' --env 'DB_PORT=3307' --env 'GITLAB_SECRETS_DB_KEY_BASE=gitlab-key' --env 'GITLAB_CI_SECRETS_DB_KEY_BASE=gitlab-ci-key' --env 'GITLAB_GRAVATAR_ENABLED=false' --env 'GITLAB_TIMEZONE=Chennai' sameersbn/gitlab:8.0.5-1

Please help

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the supplied docker run command, focusing on the GITLAB_BACKUPS, GITLAB_BACKUP_TIME, and GITLAB_BACKUP_DIR settings and the mounted /home/git/gitlab path. Check the container's mounted logs for backup-related output and verify whether a backup tar is created under the configured directory; the issue is resolved when the scheduled tar appears there.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, shell
Domain
devops, infrastructure
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.