By zita13
Hi,
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:
ingress:
enabled: true
hosts:
- registry.your_domain
annotations:
kubernetes.io/ingress.class: nginx
cert-manager.io/cluster-issuer: letsencrypt-prod
nginx.ingress.kubernetes.io/proxy-body-size: "30720m"
tls:
- secretName: docker-registry-prod
hosts:
- 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.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
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!
https://www.digitalocean.com/docs/images/container-registry/
Regards,
John Kwiatkoski Senior Developer Support Engineer - Kubernetes
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.