The command sequence is simple:ĭocker pull myhost:8081/elasticsearch/elasticsearch:7.13.3 I downloaded it from github, untarred it on a folder and setup an alias to invoke it without specifying a path.
The first step was creating a certificate using Easy-RSA. Setting up the registry (part I)įor setting the registry I followed Maarten Tijhof’s guide, except for the private registry, but I ended with and “insecure” registry.īut It was working pretty well, first for registered users, and after redeploying nexus, for unauthenticated too.Īfter pulling several images, I was able to see some data cached using the browser view.Īs configuring a SSL listener directly on nexus was a bit tedious, the official documentation and forums recommended using in front of nexus, and having nexus running using docker-compose, made setting up nginx a piece of cake. The last question of the wizard was about telemetry, the choice is on you. So I recommend to enable anonymous access through the wizard. I chose mine and moved to another important question: allowing anonymous access.Īt my first attempt I selected disabling anonymous access, but enabling it later was full of troubles, I even had to destroy the volume and deploy nexus again, event it was working perfectly with logged in users. The first thing I got was a small config wizard (5 steps), the first and more important thing was changing the admin password. Once started I pointed my browser to and the nexus interface was waiting for me.įor signing in, I was requested the admin password, it was an autogenerated password which looked like an UUID, and it was stored on /nexus-data/admin.password inside the container and, in my case, the binded volume. nexus-data:/nexus-data restart: on- failure ports: Image: sonatype/nexus3 container_name: nexus volumes:
0 kommentar(er)
