sameersbn / sameersbn/docker-gitlab
public key invalid after the docker gitlab recreate
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
hello, I have set the mirror repository of a gitlab's repository for syncing change to github's repo, the protocol I use is ssh, I have add the mirror repository's public key to the github repository's deploy key list.
but when I recreate the gitlab docker container, it seems the public key not work?
how to fix?
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 files or tests are named. Start by reviewing how the GitLab Docker container stores SSH or mirror credentials and what is recreated when the container is replaced. Done means identifying the persistence or key configuration involved and confirming that the GitLab mirror still authenticates with GitHub after recreation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, git, gitlab
- Domain
- authentication, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100