sameersbn / sameersbn/docker-gitlab
How To Restore Gitlab After Failed Upgrade?
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
My entire gitlab server is hosted.
I am using Sameersbn/docker-gitlab:8.2.3 though Synoloyg NAS. After upgrading their DSM to 6.0, gitlab filed to start. I decided to backup the gitlab directory (with the repositories, backups, etc.). Then I removed the Gitlab docker image and tried to reinstall. That failed too and is still failing.
I want to big up sameersbn/docker-gitlab:8.2.3 on a linux box with external mysql server and redis container. Oh, the mysql db for gitlab was deleted by Synology when I used the package manager to remove gitlab.
With the back up files, can i restore my gitlab to the way it was before using a clean setup on another server?
I would greatly appreciate some urgent help on this matter. Developers are unable to commit and share.
Thanks.
.v
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
No repository file or test is named. Start by reviewing the backed-up GitLab directory and the docker-gitlab:8.2.3 setup, including the external MySQL database and Redis container. Done would mean determining whether the backup can restore the service on a clean Linux host.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, linux, mysql, redis
- Domain
- database, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100