sameersbn / sameersbn/docker-gitlab
Repeated cron backup jobs
Open
Nobody has claimed this yet.
wontfix
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Hi, we've been using sameersbn/gitlab:8.12.5 docker image for a while and noticed this (run inside a container):
root@2ecfcd1201cb:/home/git/gitlab# head /var/spool/cron/crontabs/git
# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (/tmp/cron.git installed on Sat Mar 11 10:25:46 2017)
# (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $)
00 23 * * * /bin/bash -l -c 'cd /home/git/gitlab && bundle exec rake gitlab:backup:create SKIP= RAILS_ENV=production'
00 23 * * * /bin/bash -l -c 'cd /home/git/gitlab && bundle exec rake gitlab:backup:create SKIP= RAILS_ENV=production'
00 23 * * * /bin/bash -l -c 'cd /home/git/gitlab && bundle exec rake gitlab:backup:create SKIP= RAILS_ENV=production'
root@2ecfcd1201cb:/home/git/gitlab# cat /var/spool/cron/crontabs/git | wc -l
120
~120 lines of backup jobs. I believe it was configured on each container start?
Besides that, thank you for maintaining gitlab docker image :) .
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 issue in the sameersbn/gitlab:8.12.5 container and inspect /var/spool/cron/crontabs/git, then trace the container startup setup that installs the backup job. Done means repeated starts no longer add duplicate backup entries and the intended schedule remains present.
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
- Mostly clear
- Newbie friendliness
- 35/100