klo2k / nexus3-docker Goto Github PK

ARM Docker image of Sonatype Nexus Repository Manager (NXRM) (Raspberry Pis - armv7l, aarch64)

License: GNU General Public License v3.0

Dockerfile 100.00%

arm arm64 docker raspberry-pi repository artifact-repository

nexus3-docker's Introduction

Sonatype Nexus 3 on ARM

Run Sonatype Sonatype Nexus Repository Manager (NXRM) on ARM hardware (e.g. Raspberry Pi) - both 32-bit (armv7l) and 64-bit (aarch64).

Nexus doesn't provide an official image to run on Raspberry Pi.

So I'm creating one and sharing it with everyone :-) .

(For x64, use the official image - sonatype/nexus3)

Running

docker run -d -p 8081:8081 --name nexus klo2k/nexus3

Building with "docker buildx" locally

Initialise buildx, if you're on a x64 machine:

# Enable ARM support
docker run --rm --privileged multiarch/qemu-user-static --reset --persistent yes

# Create 'mybuilder' if not exist, set as default builder
docker buildx inspect mybuilder||docker buildx create --name mybuilder
docker buildx use mybuilder

# Start builder
docker buildx inspect --bootstrap

Build ARM 32-bit (armv7l):

docker buildx build --pull \
  --platform "linux/arm/v7" \
  --tag "klo2k/nexus3" \
  --output=type=docker \
  .

Build ARM 64-bit (aarch64):

docker buildx build --pull \
  --platform "linux/arm64" \
  --tag "klo2k/nexus3" \
  --output=type=docker \
  .

Credits

Nexus Team: For the awesome repo, and their Dockerfile
Dan Rollo (bhamail): For the jna-platform jar hack
Henry Wang (HenryQW): For Docker buildx Github Action

nexus3-docker's People

Contributors

Stargazers

Watchers

nexus3-docker's Issues

username and password

what is default username and password of nexus

Improve build performance - cache nexus.tar.gz and jars

From #10 , we can improve build performance, by reducing the stuff we need to download every time we build.

As suggested, we can use wget instead of ADD to cache layer (ADD doesn't cache)

Bump nexus3 version ton 3.66

Hi :)

First of all, thanks for this image, which saves me a tons of time !
Is it possible to re-run the pipeline to get the latest version of nexus3 ?

I checked the github actions and realised you had a way to extract the latest main version number. I suppose a "simple" rerun of the action pipeline can upgrade the image ?

Official dockerfile arm64 build is working now

FYI

https://github.com/sonatype/docker-nexus3/blob/master/Dockerfile

arm64 machine (k3s-arm64) to build and run

After build and run, no error log found in normal use (I only used maven repo, docker repo).

update nexus to version 3.68.1 or later(critical vulnerability)

Current version of nexus has a critical security vulnerbility
https://support.sonatype.com/hc/en-us/articles/29416509323923-CVE-2024-4956-Nexus-Repository-3-Path-Traversal-2024-05-16
can you please update it to latest one?

Warning in Memory Size

Hello, Thanks for nice image.

I have just tried and found out this warning. Is it possible to correct it? Thanks.

*SYSTEM com.orientechnologies.common.util.OMemory - Configured maximum amount of memory available to the cache (4294967296 bytes) is larger than configured JVM maximum direct memory size (2147483648 bytes). That may cause out of memory errors, please tune the configuration up. Use the -XX:MaxDirectMemorySize JVM option to raise the JVM maximum direct memory size or storage.diskCache.bufferSize OrientDB option to lower memory requirements of the cache.

How frequently do you release?

Current version of Sonatype Nexus Repository is 3.61.0.

How frequently do you release arm64 images? Latest version build with your tool submitted to docker hub is 3.43.0.

GitHub --> Docker Hub CI

Automate build to Dockerhub
https://www.henry.wang/2019/12/05/arm-dockerhub.html

klo2k/nexus3 could not run on an AWS ARM EC2 instance

Hello, I would like to ask for a bit of assistance on setting up the nexus3 docker on AWS EC2 (aarch64)

This is what I have done:

Set up an AWS EC2 instance (Ubuntu 22.04.3 LTS, t4g.micro, access to port 80/443/8081, otherwise its all standard settings)
In EC2 instance: Install Docker
In EC2 instance: sudo docker run -d -p 8081:8081 --name nexus klo2k/nexus3

These are the symptoms:
This is what happened when I executed sudo docker ps -a after around a minute:

CONTAINER ID   IMAGE          COMMAND                  CREATED          STATUS                        PORTS     NAMES
1d2f53f17d9a   klo2k/nexus3   "/opt/sonatype/nexus…"   54 seconds ago   Exited (137) 34 seconds ago             nexus

I have also included the execution of the docker logs retrieval below: sudo docker logs nexus
klo2k-nexus.log

I have tried looking into the logs myself, and I find that its very sparse when it comes to ERROR messages.
These are the closest things that I see could indicate an issue:

...
2023-11-02 03:14:43,341+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.pax.logging.NexusLogActivator - start
2023-11-02 03:14:43,575+0000 WARN  [CM Event Dispatcher (Fire ConfigurationEvent: pid=org.apache.karaf.log)] *SYSTEM org.apache.felix.fileinstall - File is not writeable: file:/opt/sonatype/nexus/etc/karaf/org.apache.karaf.log.cfg
2023-11-02 03:14:43,581+0000 WARN  [CM Event Dispatcher (Fire ConfigurationEvent: pid=jmx.acl)] *SYSTEM org.apache.felix.fileinstall - File is not writeable: file:/opt/sonatype/nexus/etc/karaf/jmx.acl.cfg
2023-11-02 03:14:43,591+0000 WARN  [CM Event Dispatcher (Fire ConfigurationEvent: pid=org.ops4j.pax.url.mvn)] *SYSTEM org.apache.felix.fileinstall - File is not writeable: file:/opt/sonatype/nexus/etc/karaf/org.ops4j.pax.url.mvn.cfg
2023-11-02 03:14:43,602+0000 WARN  [CM Event Dispatcher (Fire ConfigurationEvent: pid=org.apache.karaf.features)] *SYSTEM org.apache.felix.fileinstall - File is not writeable: file:/opt/sonatype/nexus/etc/karaf/org.apache.karaf.features.cfg
2023-11-02 03:14:43,610+0000 WARN  [CM Event Dispatcher (Fire ConfigurationEvent: pid=org.apache.felix.fileinstall~deploy)] *SYSTEM org.apache.felix.fileinstall - File is not writeable: file:/opt/sonatype/nexus/etc/karaf/org.apache.felix.fileinstall-deploy.cfg
2023-11-02 03:14:43,616+0000 WARN  [CM Event Dispatcher (Fire ConfigurationEvent: pid=profile)] *SYSTEM org.apache.felix.fileinstall - File is not writeable: file:/opt/sonatype/nexus/etc/karaf/profile.cfg
2023-11-02 03:14:43,621+0000 WARN  [CM Event Dispatcher (Fire ConfigurationEvent: pid=org.apache.karaf.kar)] *SYSTEM org.apache.felix.fileinstall - File is not writeable: file:/opt/sonatype/nexus/etc/karaf/org.apache.karaf.kar.cfg
2023-11-02 03:14:43,627+0000 WARN  [CM Event Dispatcher (Fire ConfigurationEvent: pid=org.apache.karaf.shell)] *SYSTEM org.apache.felix.fileinstall - File is not writeable: file:/opt/sonatype/nexus/etc/karaf/org.apache.karaf.shell.cfg
2023-11-02 03:14:43,633+0000 WARN  [CM Event Dispatcher (Fire ConfigurationEvent: pid=org.apache.karaf.service.acl.command)] *SYSTEM org.apache.felix.fileinstall - File is not writeable: file:/opt/sonatype/nexus/etc/karaf/org.apache.karaf.service.acl.command.cfg
2023-11-02 03:14:43,638+0000 WARN  [CM Event Dispatcher (Fire ConfigurationEvent: pid=org.apache.karaf.management)] *SYSTEM org.apache.felix.fileinstall - File is not writeable: file:/opt/sonatype/nexus/etc/karaf/org.apache.karaf.management.cfg
2023-11-02 03:14:43,644+0000 WARN  [CM Event Dispatcher (Fire ConfigurationEvent: pid=org.ops4j.pax.logging)] *SYSTEM org.apache.felix.fileinstall - File is not writeable: file:/opt/sonatype/nexus/etc/karaf/org.ops4j.pax.logging.cfg
2023-11-02 03:14:43,649+0000 WARN  [CM Event Dispatcher (Fire ConfigurationEvent: pid=org.apache.karaf.jaas)] *SYSTEM org.apache.felix.fileinstall - File is not writeable: file:/opt/sonatype/nexus/etc/karaf/org.apache.karaf.jaas.cfg
2023-11-02 03:14:43,991+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.features.internal.FeaturesWrapper - Fast FeaturesService starting
...
2023-11-02 03:14:45,962+0000 WARN  [FelixStartLevel] *SYSTEM uk.org.lidalia.sysoutslf4j.context.SysOutOverSLF4JInitialiser - Your logging framework class org.ops4j.pax.logging.slf4j.Slf4jLogger is not known - if it needs access to the standard println methods on the console you will need to register it by calling registerLoggingSystemPackage
...

Other than that, I don't really have anything else to go off of.

Please let me know if you have any questions.

Thanks in advance,
Henry

Create Java 11 Docker Images

Sonatype provides Docker images running on Java 11 instead of Java 8. Java 11 is much more Docker-aware than Java 8 (JVM 8 is actually completely container unaware). It would be nice to have Java 11 ARM images.

License

Hi, could you please add a license to the repo? Thanks :)

Base image is too old - need to use up-to-date base image

#10 got me thinking - it's a good opportunity to use up-to-date base image for security reasons.

We shouldn't let #4 keeps us forever on ancient ubuntu:focal-20200115...

Current development build startup hang with "OpenJDK Client VM warning: No monotonic clock was available" error + 400% CPU

When trying to test #3, current development build is failing to start, while CPU is pegged at 400%

docker log:

OpenJDK Client VM warning: No monotonic clock was available - timed services may be adversely affected if the time-of-day clock changes
1969-12-31 23:59:58,000+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.pax.logging.NexusLogActivator - start

Steps to reproduce

docker pull klo2k/nexus3:development
docker run --rm --detached klo2k/nexus3:development

Unable to download scoped repos in Nexus

I have a containerized Nexus3 repo v 3.43.0-01 using this image that I've successfully published a package to:

However, when attempting to download this package via npm i,

I receive the following error

This is a scoped repo, defined as "@my-scope/tinymce": "4.1.0"

The only thing I've been able to find so far is that it's probably due to the encoded slash in the scope, but that appears to have been fixed since 3.17. I'm not running through a proxy, it's just a local container. It looks like Nexus is served via Jetty Server, but I'm not able to find a way to allow encoded slashes. Any help greatly appreciated!

failed to map segment from shared object

There is a bug on raspberry pi arm64 ubuntu
java.lang.UnsatisfiedLinkError: /nexus-data/tmp/jna1594202494393200442.tmp: /nexus-data/tmp/jna1594202494393200442.tmp: failed to map segment from shared object

Please tell me how to fix it. thanks