How to correctly handle certificates and secrets for private docker registry.

Posted June 10, 2020 1.9k views
DockerKubernetesDigitalOcean Managed Kubernetes


I have followed this tutorial, but I get

Error response from daemon: login attempt to https://space.registered-domain/v2/ failed with status: 403 Forbidden

To give some context, I am working from a workstation which has no domain name assigned to it and cannot access it from the outside (it is behind a router firewall from an ISP). Would those be a prerequisite to be able to interact with the private docker registry ? In the tutorial, the ingress is:

  enabled: true
    - registry.your_domain
  annotations: nginx letsencrypt-prod "30720m"
    - secretName: docker-registry-prod
        - registry.your_domain

Is the ‘registry.your_domain’ the domain I registered on my digitalocean kubernetes cluster or the one for my workstation ?

Thanks for any clarifications.

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Submit an Answer
1 answer

The registry.your_domain is the hostname that resolves to your registry in Kubernetes cluster. I would look now into the DOCR product we offer!


John Kwiatkoski
Senior Developer Support Engineer - Kubernetes