Docker Nexus 3.15.2 to Docker Nexus 3.16.1

[kbri...@gmail.com]

So I have a local host volume mount that consists of all config, storage and logs for a dockerized Nexus 3.15.2. I'm trying to upgrade to Dockerized Nexus 3.16.1. 

The steps I'm performing are the following:

1. docker stop nexus 3.15.2
2. docker run -d -p 8081:8081 --name nexus -v /usr/local/nexus-data:/nexus-data sonatype/nexus3 (to start up the latest docker, the mount is using the pre-existing mount that 3.15.2 was using)
   
3. Verify Nexus UI is up and running.

Nexus is up and running but its still using 3.15.2, I'm assuming there are files that are referencing 3.15.2 that are taking precedence over what the version of the new container is using (in this case 3.16.1)

Is there some sort of guide as to what needs to be replaced on the local host mount or is there a another procedure to migrate from a dockerized 3.15.2 to a dockerized 3.16.1?

Thanks in advance

[Rich Seddon]

What you've done should be all that is needed. I wonder if the old version was cached....can you try clearing your browsers cache?

[Artur Frysiak]

Hi

You should include image tag in docker run command:

docker run -d -p 8081:8081 --name nexus -v /usr/local/nexus-data:/nexus-data sonatype/nexus3:3.16.1

Regards

Artur Frysiak

--
You received this message because you are subscribed to the Google Groups "Nexus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nexus-users...@glists.sonatype.com.
To post to this group, send email to nexus...@glists.sonatype.com.
To view this discussion on the web visit https://groups.google.com/a/glists.sonatype.com/d/msgid/nexus-users/64922e3c-8491-4569-8b01-dcd6195f7f12%40glists.sonatype.com.
For more options, visit https://groups.google.com/a/glists.sonatype.com/d/optout.

[Kevin Brizida]

So I made sure I emptied cache and did a hard reload in chrome and it didn't work. I know yesterday I tried using :latest as my tag and that also didn't work. 

Tried Artur's suggestion this morning and that seemed to do the trick. Thank you all for the suggestions and the help. 

Yesterday i grep'd the volume that was mounted an there were tons of references to 3.15.2 in there still so I thought I had to manually replace the version with some type of sed cmd. Found it odd that my first attempt didn't work properly by leaving the tag off, I assume no tag means it grabs the latest but I couldn't get it to pull the newer version. With Artur's suggestion he pull's complete. I think the pull for new versions didn't occur when my original attempts.

[Artur Frysiak]

"docker run" command will not fetch new version of "image:latest" if any version is already available locally. You can refresh image using "docker pull" command.

The good practice is to not use "latest" tag but to specify version.