sameersbn / sameersbn/docker-gitlab
gitlab cant't recovery!
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
gitlab version: 11.4.6
run command errror for "bundle exec rake gitlab:backup:restore BACKUP=/home/git/data/backups"/1640887316_2021_12_30_11.4.6_gitlab_backup.tar
bundler: failed to load command: rake (/usr/bin/rake)
Gem::GemNotFoundException: can't find gem rake (>= 0.a)
/usr/lib/ruby/2.4.0/rubygems.rb:271:in find_spec_for_exe'
/usr/lib/ruby/2.4.0/rubygems.rb:299:in activate_bin_path'
/usr/bin/rake:23:in `<top (required)>'
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 by reproducing the backup restore command in the GitLab 11.4.6 environment and inspect the reported Gem::GemNotFoundException for rake. The issue is resolved when the documented restore command completes successfully, but no file or test is identified in the report.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, ruby
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100