sameersbn / sameersbn/docker-gitlab
'rsync' command missing in container
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
I tried to use rake task "gitlab:backup:create" to create backups with STRATEGY=copy as described in Gitlab documentation. But it ends up with the following error message. It seems the image has no 'rsync' command available.
rake aborted!
Errno::ENOENT: No such file or directory - rsync
/home/git/gitlab/lib/gitlab/popen.rb:36:in `popen_with_detail'
/home/git/gitlab/lib/gitlab/popen.rb:12:in `popen'
/home/git/gitlab/lib/backup/files.rb:22:in `dump'
/home/git/gitlab/lib/tasks/gitlab/backup.rake:139:in `block (4 levels) in <top (required)>'
/home/git/gitlab/lib/tasks/gitlab/backup.rake:13:in `block (3 levels) in <top (required)>'
/home/git/gitlab/vendor/bundle/ruby/2.3.0/gems/rake-12.3.0/exe/rake:27:in `<top (required)>'
Tasks: TOP => gitlab:backup:uploads:create
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 the backup flow in lib/backup/files.rb and lib/tasks/gitlab/backup.rake, then inspect the container build configuration for dependencies used by gitlab:backup:create. Reproduce the STRATEGY=copy failure and consider the issue done when the container provides rsync and the backup path no longer raises Errno::ENOENT.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100