You need to specify to your Docker client that you want to use an insecure registry. So the error consists of 3 parts that are interrelated. Now you get either the error I showed you above or http: server gave HTTP response to HTTPS client Understand and Fix the Errors Then push the image docker push .com:8083/nanoserver In order to push an images to this registry you have to tag a default image to this registry docker tag microsoft/nanoserver

(note that the default Nexus Username / Password is admin/admin123) When everything was set up correctly, I set up my Docker for Windows Client to use Windows Containers, and logged in to the registry. So in the Azure Portal ( or with the CLI) open the inbound ports for 8082, 80 to access your Nexus server Using the registry To make this accessible, the ports on the network security group should be opened as well. I ended up with a private repository on port 8083 and a proxy for Docker Hub on port 8082 on my public IP address of my Linux machine on Azure. On this machine I ran the Nexus3 Docker Container, to get a fresh Nexus3 installation docker run -p 8081:8081 -p 8082:8082 -p 8083:8083 sonatype/nexus3Īfter that I configured my Nexus as described in this post.

To get started easily I spun up a Linux Machine on Azure with Docker Installed. (Spoiler alert: it is not a Windows Container problem, it is a Foreign Layer Problem.) Setting up a Demo Environment

In first instance I thought that it was that Sonatype did not support Windows Containers or that the installation was strange, so I started fiddling with it. So we created a Windows Base container and tried to push this to the Nexus repository. Net teams are moving towards Docker, the need for Docker containers arose as well. My customer uses Sonatype Nexus as their artifact repository for all kinds of packages and also for Docker Containers.

Nexus 3 setup