Some gitlab projects return 404 error after accidentally mounting two sets of docker-compose containers to the same volumes

|▌冷眼眸甩不掉的悲伤 提交于 2019-12-25 02:52:01

问题


There's a private gitlab server in my company, which is created by using the docker-compose file of sameersbn/docker-gitlab:10.5.6.

Today when I try to move the mounted volumes to a new disk, I accidentally created 2 sets of docker containers(sameersbn/gitlab:10.5.6, sameersbn/postgresql:9.6-2, and sameersbn/redis:2.8.4) that use the same disk volumes.

Then a moment later, someone in the company told me that his project at gitlab returns 404 error.

I've checked the PostgreSQL database and found that the project still exists in the database. I mean SELECT * FROM projects WHERE name ='<project_name>'; returns data.

If I create a new empty project with the same name, I got Name has already been taken error.

Are there any ways to fix this problem?

It looks like that something got nasty inside the database, which causes the project to return 404 error when visiting the webpage.

来源:https://stackoverflow.com/questions/54760637/some-gitlab-projects-return-404-error-after-accidentally-mounting-two-sets-of-do

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!