sameersbn / sameersbn/docker-gitlab
docker login returns error 500
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
While setting up the registry according to the manual https://github.com/sameersbn/docker-gitlab/blob/master/docs/container_registry.md I encountered a setup problem:
When trying to authorize a user via docker login, a 500 error occurs.
docker login registry.host.com -u user --password password returns Error response from daemon: Get "https://registry.host.com/v2/": received unexpected HTTP status: 500 Internal Server Error
At the same time, there are no entries in the docker logs about the cause of the error.
After mounting /var/logs/ on the host, I was able to find out the reason: there are no access rights to the file /certs/registry.key
After chown docker:docker registry.key in certs directory, everything worked as expected.
I think it is necessary to add a check for access rights to the file to the documentation, since when running gitlab according to this manual, the error is not displayed in the docker logs.
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 docs/container_registry.md and review the documented Docker registry setup. Add a troubleshooting note covering permissions on /certs/registry.key, the resulting Docker login 500 error, and the required ownership change; done means users can diagnose this failure from the documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100