sameersbn / sameersbn/docker-gitlab
Backup error: "command":"create","error":"manager: repository empty: repository skipped"
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
My project is not empty but backup's log:
{"command":"create","error":"manager: repository empty: repository skipped","gl_project_path":"TEST/TEST","level":"warning","msg":"skipped create","relative_path":"@hashed/4a/44/4a44dc15364204a80fe80e9039455cc1608281820fe2b24f1e5233ade6af1dd5.wiki.git","storage_name":"default","time":"2022-10-25T06:50:55.709Z"}
Can you 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 by reproducing the backup command in the Dockerized GitLab setup and inspect the logged repository path, @hashed/4a/44/4a44dc15364204a80fe80e9039455cc1608281820fe2b24f1e5233ade6af1dd5.wiki.git. Determine why a non-empty project is reported as an empty repository, then verify that its backup is no longer skipped.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100