I am a devops working at a financial company and was working on the company's internal network. This video helped me set up docker proxy very easily, quickly and reliably. Additionally, if assign a domain to nexus3 and process the SSL certificate on a loadbalancer (regardless of the provider) in front of the nexus3 server, you do not need to set up insecure-registry.
Best video about this topic !!!! I struggled with many other "private registry" videos and finally (in combination with nexus), I understood the concepts much better. I missed the point about the "Docker Index"/Use Docker Hub setting which led to an "manifest unknown" error but eventually I corrected it.
Great video! I was having a hard time following the Nexus docs and figuring out the URL I should use to pull images through the proxy, and only with your video it was clear that the image name should be provided from the start of the path - and not include the repo name. There's one thing I would change in your video, though: it's not great advice to have the volume directory given permissions as 777; The reason why it fails by default is because the Nexus container expects that directory to have the ownership for the same user as the one that runs Nexus itself, which is user 200. So changing the directory ownership from whatever it is (usually user 1000 - if you're running that in a desktop through Docker for example) to 200:200 (user:group) is what fixes the issue. Cheers!
Thanks for the detail process. Question: Is there a way to tell docker to use the default repository instead of qualifying on the commmand line? I'm not happy about qualifying it on the command line. Furthermore, I do not want to see repository qualified image names with the repository especially if they are being proxied from Dockerhub.
I am a devops working at a financial company and was working on the company's internal network.
This video helped me set up docker proxy very easily, quickly and reliably.
Additionally, if assign a domain to nexus3 and process the SSL certificate on a loadbalancer (regardless of the provider) in front of the nexus3 server, you do not need to set up insecure-registry.
Exactly what I needed. Thanks for putting this together!
Best video about this topic !!!! I struggled with many other "private registry" videos and finally (in combination with nexus), I understood the concepts much better. I missed the point about the "Docker Index"/Use Docker Hub setting which led to an "manifest unknown" error but eventually I corrected it.
Excellent video. Perfectly explained step by step. Simply awesome
Great video! I was having a hard time following the Nexus docs and figuring out the URL I should use to pull images through the proxy, and only with your video it was clear that the image name should be provided from the start of the path - and not include the repo name.
There's one thing I would change in your video, though: it's not great advice to have the volume directory given permissions as 777; The reason why it fails by default is because the Nexus container expects that directory to have the ownership for the same user as the one that runs Nexus itself, which is user 200. So changing the directory ownership from whatever it is (usually user 1000 - if you're running that in a desktop through Docker for example) to 200:200 (user:group) is what fixes the issue.
Cheers!
Awesome demo of Nexus, thanks
Great content
Thanks a lot
Great video! Straight to the point. Nice. :)
i was struggling to create proxy repo you saved me
Thank you so much. Perfect explained
Excellent Video. all is perfect and perfecty explained thank you
Hi Chris and thank you for the useful tutorial.
duude i am really needed this info thank you so muchhh
Thanks for the detail process. Question: Is there a way to tell docker to use the default repository instead of qualifying on the commmand line? I'm not happy about qualifying it on the command line. Furthermore, I do not want to see repository qualified image names with the repository especially if they are being proxied from Dockerhub.
Awesome video thanks Chris. Is the followup vid ready yet?
Thank you!!!!!!!! Sonatypes own documentation is missing a ton of critical information to get their own product working with Docker Hub.
Very good!
AWESOME 🔥🔥🔥
thanks
nice video