Nexus Repository Manager 2 does not support Docker as a format. Nexus Repository Manager 3 does, and Docker support is a part of our OSS solution, meaning you can use Docker completely free. There is a professional version coming with 3.1 that will start to have features such as high availability, expanded enterprise support, as well as just regular support of the product.
As for the Docker images, Nexus 3 now has the ability to operate as OSS or Pro from the same bundle so you'll likely only see tags for Releases, not OSS and Pro.
Answer from DarthHater on Stack Overflownexus3 - Nexus 2 OSS vs. Nexus 3 - Stack Overflow
maven - How to migrate from Nexus Professional to Nexus OSS - Stack Overflow
What is your thoughts on nexus sonatype
Have you used Sonatype Nexus?
Yes, it is not a complicated task.
Install Nexus OSS on the same server. Do change the following so that the new Nexus OSS has the same configuration as the existing Nexus Professional runtime.
Configuration
- port is set in [runtime]/conf/nexus.properties
- sonatype-work directory location is set in [runtime]/conf/nexus.properties
- the java command is set in [runtime]/bin/jsw/conf/wrapper.conf
- the log directory location is set in [runtime]/conf/nexus.properties
Process
- Stop the Professional
- Make sure to backup the sonatype-work/nexus/conf directory
- Remove the professional plugins from sonatype-work/nexus/plugin-repository
- Add the p2 plugins for OSS to the sonatype-work/nexus/plugin-repository sonatype-work/nexus/conf/nexus.xml
- Remove procurement repositories references from nexus.xml
- Remove Scheduled task that use the professional plugins or features from from nexus.xml Note: Those two tasks could have been done from the Nexus Professional UI before stopping it.
- Remove User-Token-Realm from the sonatype-work/nexus/conf/security-configuration.xml
Start the Nexus OSS
- start preferably with nexus console instead of nexus start, so it shows more information
- check the [runtime]/logs/wrapper.log
- check the sonatype-work-nexus/logs/nexus.log
As a note: If your license to Nexus 3 Pro has expired, when you log in to the UI, you cannot access anything in the admin UI. You are only redirected back to the License screen with a stern warning message that you don't have a valid license.
I tried removing all Pro plugins etc as in the earlier answer. Tried finding where the Pro licenser was stored on file - but could not find any documentation from Sonatype of this. I assumed it was stored somewhere in the database.
In my case I worked with an evaluation server, so I removed the whole sonatype-work/nexus3 directory and restarted the nexus server. Even without data, it still claimed to be a Nexus Pro installation.
Finally I found the setting stored in the users home directory, in ~/.java/.userPrefs/com/sonatype of all places.
When that directory was removed/renamed I could start Nexus as a regular OSS.
It's not easy to find this in Sonatypes documentation, but they mention it in some places like: https://support.sonatype.com/hc/en-us/articles/213465018-Every-time-Nexus-is-restarted-it-asks-for-the-license-to-be-installed-
I have Sonatype Nexus RepositoryOSS 3.74.0-05 and it crashes all the time and we are thinking to move to a new version or another alternative. Hows your experience?
How does it compare to GitLab, GitHub, and others out there? Has ownership by Private Equity firm hurt its development and support?
I started a job at a company that relies on Nexus Repository Manager. From what I saw and researched its primary use-case is storing and distributing artifacts of various kinds coming from CI frameworks such as jenkins (also part of the companies stack).
In the past I made heavy use of gitlab, azure (I'm not the biggest fan of azure but it is used at that company as well) and github which all (if I'm not mistaken) come with ways to handle artifacts. I'm wondering if there are reasons to still support that stack (azure, jenkins, nexus) or to transition fully to azure as this should be able to handle all these requirements but in a single place.