sameersbn / sameersbn/docker-gitlab
error while restore backup
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
hi every body
i take a full backup from my Gitlab and for test i run another Gitlab at other VM and i want to restore my main backup on Gitlab test . i copy backup file from main gitlab backup directory to secondary gitlab backup directory . when i used : "docker-compose run --rm gitlab app:rake gitlab:backup:restore BACKUP=1534620980_2018_08_18_10.0.3_gitlab_backup.tar_gitlab_backup.tar" command to restore my backup show this error :
Missing Rails.application.secrets.jws_private_key for production environment. The secret will be generated and stored in config/secrets.yml.
The backup file 1534620980_2018_08_18_10.0.3_gitlab_backup.tar_gitlab_backup.tar does not exist!
thankfully if help me
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 docker-compose run command and the gitlab:backup:restore task shown in the report. Check the backup directory and the exact archive filename used by the command, then reproduce the restore attempt in a test GitLab container. Done means the backup is found and the reported restore error is resolved, but the issue does not name a source file or test.
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
- 20/100