sameersbn / sameersbn/docker-gitlab

gitlab docker registry exception

Open
#1,315 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

wontfix
Dominant language
Shell
Stars
8.1k
Forks
2.1k
Avg merge
17h 47m
Merged PRs (30d)
7

Description

I config as https://github.com/sameersbn/docker-gitlab/blob/master/docs/container_registry.md,But when I visit the gitlab project registry,it throw exception

image

postgresql_1  | LOG:  autovacuum launcher started
registry_1    | 2017/08/01 03:17:24 http: TLS handshake error from 172.18.0.5:44478: remote error: unknown certificate authority
registry_1    | 2017/08/01 03:17:24 http: TLS handshake error from 172.18.0.5:44482: remote error: unknown certificate authority
registry_1    | time="2017-08-01T03:15:57.86794915Z" level=info msg="redis not configured" go.version=go1.6.2 instance.id=75361df8-2d83-4127-b341-7dc0b01aac68 service=registry version=v2.4.1 
registry_1    | time="2017-08-01T03:15:57.868189065Z" level=info msg="Starting upload purge in 43m0s" go.version=go1.6.2 instance.id=75361df8-2d83-4127-b341-7dc0b01aac68 service=registry version=v2.4.1 
registry_1    | time="2017-08-01T03:15:57.917945306Z" level=info msg="using inmemory blob descriptor cache" go.version=go1.6.2 instance.id=75361df8-2d83-4127-b341-7dc0b01aac68 service=registry version=v2.4.1 
registry_1    | time="2017-08-01T03:15:57.973284849Z" level=info msg="listening on [::]:5000, tls" go.version=go1.6.2 instance.id=75361df8-2d83-4127-b341-7dc0b01aac68 service=registry version=v2.4.1 
registry_1    | 2017/08/01 03:17:24 http: TLS handshake error from 172.18.0.5:44478: remote error: unknown certificate authority
registry_1    | 2017/08/01 03:17:24 http: TLS handshake error from 172.18.0.5:44482: remote error: unknown certificate authority
registry_1    | time="2017-08-01T03:23:17.689118547Z" level=info msg="redis not configured" go.version=go1.6.2 instance.id=58ea19bc-081a-4d7f-bc70-b61e09a576eb service=registry version=v2.4.1 
registry_1    | time="2017-08-01T03:23:17.68913287Z" level=info msg="Starting upload purge in 21m0s" go.version=go1.6.2 instance.id=58ea19bc-081a-4d7f-bc70-b61e09a576eb service=registry version=v2.4.1 
registry_1    | time="2017-08-01T03:23:17.70543504Z" level=info msg="using inmemory blob descriptor cache" go.version=go1.6.2 instance.id=58ea19bc-081a-4d7f-bc70-b61e09a576eb service=registry version=v2.4.1 
registry_1    | time="2017-08-01T03:23:17.70681793Z" level=info msg="listening on [::]:5000, tls" go.version=go1.6.2 instance.id=58ea19bc-081a-4d7f-bc70-b61e09a576eb service=registry version=v2.4.1 
registry_1    | 2017/08/01 03:23:46 http: TLS handshake error from 172.18.0.5:44498: remote error: unknown certificate authority
registry_1    | 2017/08/01 03:23:47 http: TLS handshake error from 172.18.0.5:44508: remote error: unknown certificate authority

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with docs/container_registry.md and compare the reported registry configuration with the TLS handshake errors in the issue log. Verify the certificate trust and registry connection path; done means the GitLab project registry can be visited without unknown-certificate-authority errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, shell
Domain
devops, infrastructure, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.