sameersbn / sameersbn/docker-gitlab
Recovery of postgresql database
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Hi! I want to begin by telling you how great and useful this project is for the community - Keep up the good work!
I recently saw that my server was down and accidentally executed docker-compose up instead of docker-compose restart. After I did that I am now getting the following error message:
ERROR: for postgresql_gitlab Cannot create container for service postgresql: Conflict. The container name "/postgresql_gitlab" is already in use by container "3cb3fa0dd9710d0152bdd5f78caa2d283bf360096bcd22d7814f6826d6410c56"Starting nginx_letsencrypt_gitlab ... done
ERROR: for postgresql Cannot create container for service postgresql: Conflict. The container name "/postgresql_gitlab" is already in use by container "3cb3fa0dd9710d0152bdd5f78caa2d283bf360096bcd22d7814f6826d6410c56". You have to remove (or rename) that container to be able to reuse that name.
ERROR: for redis Cannot create container for service redis: Conflict. The container name "/redis_gitlab" is already in use by container "981a6ddc947e9b4623b3b129fb304229e7089bd4640fe15f9121b7b3bb3b0602". You have to remove (or rename) that container to be able to reuse that name.
ERROR: Encountered errors while bringing up the project.
I really want to use that database since I have a lot of projects in there. What can I do to fix this issue?
Thank you in advance!
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 services named in the report, especially postgresql and redis, and inspect the existing container names and the difference between docker-compose up and docker-compose restart. Confirm that the PostgreSQL data remains available while resolving the container conflict, then verify that the affected services start without losing the stored projects.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, postgresql
- Domain
- databases, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100