org.eclipse.jetty.util.component.AbstractLifeCycle - FAILED com.yammer.metrics.jetty.InstrumentedHandler@50a949a8: java.lang.IllegalStateException: Nexus work directory already in use: /sonatype-work java.lang.IllegalStateException: Nexus work directory already in use: /sonatype-work at com.google.common.base.Preconditions.checkState(Preconditions.java:200) at org.sonatype.nexus.webapp.WebappBootstrap.contextInitialized(WebappBootstrap.java:117) at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:782) at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:424) at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:774) at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:249) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1242) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:717) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:494) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95) at org.eclipse.jetty.server.Server.doStart(Server.java:282) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) at org.sonatype.nexus.bootstrap.jetty.JettyServer$JettyMainThread.run(JettyServer.java:247) 2018-08-01 12:39:27,387+0000 WARN [jetty-main-1] org.eclipse.jetty.util.component.AbstractLifeCycle - FAILED org.eclipse.jetty.server.handler.HandlerCollection@3f344023: java.lang.IllegalStateException: Nexus work directory already in use: /sonatype-work java.lang.IllegalStateException: Nexus work directory already in use: /sonatype-work at com.google.common.base.Preconditions.checkState(Preconditions.java:200) at org.sonatype.nexus.webapp.WebappBootstrap.contextInitialized(WebappBootstrap.java:117) at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:782) at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:424) at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:774) at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:249) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1242) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:717) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:494) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95) at org.eclipse.jetty.server.Server.doStart(Server.java:282) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) at org.sonatype.nexus.bootstrap.jetty.JettyServer$JettyMainThread.run(JettyServer.java:247) 2018-08-01 12:39:27,387+0000 WARN [jetty-main-1] org.eclipse.jetty.util.component.AbstractLifeCycle - FAILED org.eclipse.jetty.server.Server@9b29df6: java.lang.IllegalStateException: Nexus work directory already in use: /sonatype-work java.lang.IllegalStateException: Nexus work directory already in use: /sonatype-work at com.google.common.base.Preconditions.checkState(Preconditions.java:200) at org.sonatype.nexus.webapp.WebappBootstrap.contextInitialized(WebappBootstrap.java:117) at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:782) at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:424) at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:774) at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:249) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1242) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:717) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:494) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95) at org.eclipse.jetty.server.Server.doStart(Server.java:282) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) at org.sonatype.nexus.bootstrap.jetty.JettyServer$JettyMainThread.run(JettyServer.java:247) 2018-08-01 12:39:27,387+0000 INFO [jetty-main-1] org.sonatype.nexus.bootstrap.jetty.JettyServer - Running 2018-08-01 12:39:27,388+0000 ERROR [main] *SYSTEM org.sonatype.nexus.bootstrap.jetty.JettyServer - Start failed java.lang.IllegalStateException: Nexus work directory already in use: /sonatype-work at com.google.common.base.Preconditions.checkState(Preconditions.java:200) at org.sonatype.nexus.webapp.WebappBootstrap.contextInitialized(WebappBootstrap.java:117) at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:782) at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:424) at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:774) at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:249) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1242) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:717) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:494) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95) at org.eclipse.jetty.server.Server.doStart(Server.java:282) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) at org.sonatype.nexus.bootstrap.jetty.JettyServer$JettyMainThread.run(JettyServer.java:247) Exception in thread "main" java.lang.IllegalStateException: Nexus work directory already in use: /sonatype-work at com.google.common.base.Preconditions.checkState(Preconditions.java:200) at org.sonatype.nexus.webapp.WebappBootstrap.contextInitialized(WebappBootstrap.java:117) at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:782) at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:424) at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:774) at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:249) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1242) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:717) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:494) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95) at org.eclipse.jetty.server.Server.doStart(Server.java:282) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) at

Hello !

I'm running nexus on my machine using a reverse_proxy, nginx in my case, when accessing nexus web interface from localhost:8081 it works just fine, but when i try to access it from the reverse proxy, nexus fails to load all the javascript css and images.

I already enabled the Base URL capability, and copied the procedure in the documentation.

Thank you for your help !

Setting the context path using NEXUS_CONTEXT causes a 404 error when using the nexus3 image:

Problem accessing /. Reason: Not Found

The logs indicate it is set properly (using NEXUS_CONTEXT=nexus/content)

nexus-context-path='/nexus/content'

Maybe image builds aren't being triggered correctly?

Also maybe It's a good idea to tag the patch releases individually so that it's easier to revert to a previous version for whatever reason.

Openshift provides a way to rsync files into a container. This is useful when moving a lot of files to a cloud deployment
https://docs.openshift.org/latest/dev_guide/copy_files_to_container.html

For the yum command, please add rsync.

Thanks

I'm using this and it works well. However, first time I spin up the container, I need to login to Nexus and create the repository. Henceforth it is persistent.

Is there a way that I may be able to create at least one repository in the container so that wen I spin up, the repository is already there?

Use data volume containers using host mounted paths as recommended by Docker. What you do here is suggesting users to run a data container using container FS path. IE users will lose their data if they destroy the data container.

Pasting in the suggested procedure from Docker:

Creating and mounting a data volume container

If you have some persistent data that you want to share between containers, or want to use from non-persistent containers, it’s best to create a named Data Volume Container, and then to mount the data from it.

Let’s create a new named container with a volume to share. While this container doesn’t run an application, it reuses the training/postgres image so that all containers are using layers in common, saving disk space.

$ docker create -v /dbdata --name dbstore training/postgres /bin/true
You can then use the --volumes-from flag to mount the /dbdata volume in another container.

$ docker run -d --volumes-from dbstore --name db1 training/postgres

What is the root-password for the docker container? It would be needed immensely much

Your current docker image is based on version 2.11.3-01, but there is already a version 2.11.4-01 available. Can you please make sure to always provide an up-to-date image when you make a release?

Some use cases requires createrepo and mergerepo commands (both delivered by createrepo package). Thos is unfortunately not a part of official docker image.
Can you please add that? In case of EL7 which is used as a base it uses 207kB of HDD space, which should not be an issue.

Sincerely,
Grzegorz

I create a data volume like:

$ docker run -d --name nexus-data sonatype/nexus:oss /bin/true

Then I create a container with port 8081 open like:

$ docker run -d --volumes-from nexus-data --name nexus -e CONTEXT_PATH=/nexus -p 8081:8081 sonatype/nexus:oss

I wait for the page to come up at http://example.com:8081/nexus. It looks good. Then I proxy incoming traffic to /nexus to 8081 in nginx.conf like:

upstream docker_nexus {
  server example.com:8081;
}

server {
  listen 443;
  // SSL stuff
  // ....
  location /nexus {
    proxy_pass http://docker_nexus/nexus;
     ...
  }
}

..and I restart nginx. Nexus is now appearing at https://example.com/nexus. Everything looks fine, except I'm warned that the proxy is not working and I should Force base URL. I do so, noticing that my the base URL provided lacks the s in https and is formatted like: http://example.com/nexus/. I add the s and check Force Base URL and click Save.

I create a user on the site with every role and a corresponding entry in my $HOME/.m2/settings.xml with the same auth info like:

<settings>
  <servers>
    <server>
      <id>example.com</id>
      <username>user</username>
      <password>sekrit</password>
    </server>
  </servers>
</settings>

I add the default repositories to my project's pom.xml like:

  <distributionManagement>
    <repository>
      <id>example.com</id>
      <name>Releases</name>
      <url>https://example.com/nexus/content/repositories/releases</url>
    </repository>
    <snapshotRepository>
      <id>example</id>
      <name>Snapshots</name>
      <url>https://example.com/nexus/content/repositories/snapshots</url>
    </snapshotRepository>
  </distributionManagement>

When I attempt to deploy my project to the Nexus repository using mvn deploy, the container dies silently. The logs reveal no information prior to the event. This is 100% reproducible; I haven't been able to successfully deploy anything yet.

When the container is stopped, the lockfile sometimes seems not to get removed and causes nexus to not start again properly. Someone has to delete the nexus.lock file manually each time. IMHO nexus needs to remove the logfile on a docker stop and (even better) ignore/remove stale lock files on startup.

We use a private DockerHub account and we want to use Nexus as a proxy for those private images - we configured the repo following this instructions: http://stevetarver.github.io/2016/11/22/nexus-in-docker.html

By the way, we are not able to view any image from our DockerHub account on Nexus, and the images pushed to our Nexus not appears on DockerHub.

see: https://issues.sonatype.org/browse/NEXUS-19709

How to set admin password for the Docker distribution, or is there a default one?

Hi,
I've create a first container with a docker compose

services:
  nexus:
    image: sonatype/nexus3
    volumes:
      - "/etc/nexus/nexus-data:/nexus-data"
    ports:
      - "8081:8081"
volumes:
  nexus-data: {}

after having config it, would like to create a new image and keep the configuration.

so i launch the Dockerfile below in /etc/nexus

FROM sonatype/nexus3:3.22.0

ADD nexus-data ./nexus-data
EXPOSE 8081

i got the following issue :

OpenJDK 64-Bit Server VM warning: Cannot open file ../sonatype-work/nexus3/log/jvm.log due to Permission denied

Warning:  Cannot open log file: ../sonatype-work/nexus3/log/jvm.log
Warning:  Forcing option -XX:LogFile=/tmp/jvm.log
java.io.FileNotFoundException: ../sonatype-work/nexus3/tmp/i4j_ZTDnGON8hezynsMX2ZCYAVDtQog=.lock (Permission denied)
        at java.io.RandomAccessFile.open0(Native Method)
        at java.io.RandomAccessFile.open(RandomAccessFile.java:316)
        at java.io.RandomAccessFile.<init>(RandomAccessFile.java:243)
        at com.install4j.runtime.launcher.util.SingleInstance.check(SingleInstance.java:72)
        at com.install4j.runtime.launcher.util.SingleInstance.checkForCurrentLauncher(SingleInstance.java:31)
        at com.install4j.runtime.launcher.UnixLauncher.checkSingleInstance(UnixLauncher.java:88)
        at com.install4j.runtime.launcher.UnixLauncher.main(UnixLauncher.java:67)
Unable to delete file: /nexus-data/cache/bundle233/version0.0/revision.location
Unable to update instance pid: /nexus-data/instances/instance.properties (Permission denied)
Exception in thread "Thread-2" java.lang.SecurityException: Could not lock User prefs. Lock file access denied.
        at java.util.prefs.FileSystemPreferences.checkLockFile0ErrorCode(FileSystemPreferences.java:949)
        at java.util.prefs.FileSystemPreferences.lockFile(FileSystemPreferences.java:937)
        at java.util.prefs.FileSystemPreferences.sync(FileSystemPreferences.java:741)
        at java.util.prefs.FileSystemPreferences.flush(FileSystemPreferences.java:836)
        at java.util.prefs.FileSystemPreferences.syncWorld(FileSystemPreferences.java:476)
        at java.util.prefs.FileSystemPreferences.access$1200(FileSystemPreferences.java:50)
        at java.util.prefs.FileSystemPreferences$4$1.run(FileSystemPreferences.java:454)

i've check the permission and the user with a modification into the docker file and
the user configured into my copied files i've got the nexus:nexus as owner and
755 for folder and 644 for file.

HI Team,
I am getting the below issue while upgrading Nexus 2.14.9 to Nexus 3.13.

Failed: java.lang.IllegalStateException: Ingestion method FS_LINK unavailable from repository bt-travel-wildfly to blob store default. Allowed: [[DOWNLOAD]]

I am blocked because of the above issue. Can you please suggest?

Thanks
Anurag

hello, i use this image to build the nexus server,everything is all right. but when i use: docker stack deploy –c docke-compose.yml my-cluster, it would't pull the image which is missing in local. i try to use the docker compose or pull firectly, it works. even after i use docker login and try again, the problem is still there. i meet the same problem on k8, after i create the secure, i resolved. so is there any configure i miss, can someone helo me to figure it out? thanks a lots.

anonymous org.sonatype.nexus.yum.internal.task.CommandLineExecutor - Execute command : mergerepo --no-database --repo=file:[....] [...] anonymous org.sonatype.nexus.yum.internal.task.CommandLineExecutor - ovl: Error while doing RPMdb copy-up: [Errno 13] Permission denied: '/var/lib/rpm/.dbenv.lock'

Conclusion is that for nexus2 (which uses OS's RPM commands), the process needs to run as root (and not as nexus user).

For those facing this issue, the work around is to start the nexus2 overriding the user defined in Dockerfile using:
docker run -u root ...

Probably due to release of 8u151.
Just need to update some of the ENVs:
JAVA_VERSION_MINOR=151
JAVA_VERSION_BUILD=12
JAVA_DOWNLOAD_HASH=e758a0de34e24606bca991d704f6dcbf \

Hi,

we use nexus behind web proxy and it would be great if we could configure it in automated fashion via environment variable (http(s)_proxy or java_opts).

Regards,
N.

Hello,

I would like to use you docker image, but would like to use my specific settings (different passwords, clojars, etc.). What is the easiest way to extend your image so that it would use conf directory that I would provide.

I have tried something like this:

FROM sonatype/nexus:oss

COPY nexus.xml ${SONATYPE_WORK}/conf/

but without success.

Thanks

This appears to be an automated build on dockerhub, but despite new changes merging recently, it hasn't rebuilt in 23 days: https://hub.docker.com/r/sonatype/nexus/builds/

Can someone force a rebuild/publish?

@oatmealraisin fyi

Hello,
My nexus working in OpenShift POD and have envirement without internet. But I have http_proxy.
I tred to add global variables to pod:

export http_proxy=my-proxy
export https_proxy=my-proxy
export no_proxy=my-proxy

but it's doesn't work for me. How I can fixe this problem?
Maybe in nexus.properties have anything parameters?

My version
nexus 3.15.1-01
and docker image sonatype/nexus3:3.15.1

I let my docker container autoredeploy from 2.0.13 to 2.0.14, when it does this, I'm getting a 404 from / downgrading to 13 and it works again.

Use Java 8 rather than Java 7

the nexus 2 version is 3 month ago. It does not use the latest java version that support detecting the docker
runtime env
Nexus2 Image

I am trying to get docker/nexus to run, but I am running into this error: 2017-03-02 10:49:24,609-0500 WARN [jetty-main-1] *SYSTEM org.sonatype.nexus.util.LockFile - Failed to write lock file
java.io.FileNotFoundException: /opt/sonatype/nexus/nexus.lock (Permission denied)

Below is my dockerfile:
FROM dock.it.vt.edu:1100/java8:v8u121VT03
ARG BUILD_DATE
ARG PARENT
ARG VCS_REF
ARG VCS_URL
ARG VERSION
LABEL org.label-schema.vendor="DBAA [email protected]"
org.label-schema.name="Nexus"
org.label-schema.description="Base image for Nexus"
org.label-schema.build-date=$BUILD_DATE
org.label-schema.vcs-ref=$VCS_REF
org.label-schema.vcs-url=$VCS_URL
org.label-schema.version=$VERSION
org.label-schema.parent=$PARENT
org.label-schema.schema-version="1.0"

USER root

ARG NEXUS_VERSION=2.14.3-02
ARG NEXUS_DOWNLOAD_URL=https://download.sonatype.com/nexus/oss/nexus-${NEXUS_VERSION}-bundle.tar.gz
ARG NEXUS_SHA1=87c1e9b0d50dbc17d2a771ce7d98ebcf67fd140a

ENV WORKDIR /opt
ENV PATH=$WORKDIR:$PATH

do all in one step

RUN set -ex &&
mkdir -p ${WORKDIR}/sonatype/nexus
&& curl --fail --silent --location --retry 3
${NEXUS_DOWNLOAD_URL}
| gunzip
| tar -x -C /tmp nexus-${NEXUS_VERSION}
&& mv /tmp/nexus-${NEXUS_VERSION}/* ${WORKDIR}/sonatype/nexus/ \

&& chgrp -R appsadm ${WORKDIR} \

&& rm -rf /tmp/nexus-${NEXUS_VERSION}

USER appsadm

EXPOSE 8081
WORKDIR /opt/sonatype/nexus

ENV CONTEXT_PATH /nexus
ENV MAX_HEAP 768m
ENV MIN_HEAP 256m
ENV JAVA_OPTS -server -Djava.net.preferIPv4Stack=true
ENV LAUNCHER_CONF ./conf/jetty.xml ./conf/jetty-requestlog.xml
CMD ${JAVA_HOME}/bin/java
-Dnexus-work=${SONATYPE_WORK} -Dnexus-webapp-context-path=${CONTEXT_PATH}
-Xms${MIN_HEAP} -Xmx${MAX_HEAP}
-cp 'conf/:lib/*'
${JAVA_OPTS}
org.sonatype.nexus.bootstrap.Launcher ${LAUNCHER_CONF}

And yes I know I am using appsadm user. Any help would be appreciated.

Hola, me sale en la pagina el error 404, porque?
Saludos

Is there a version available for Docker on Windows 2016 that runs on native Windows and not using the Linux VM on top of Windows?

Hey folks,

I'm using an NFS drive to persist data for a Nexus 3 container. When the container starts, there is an existing blobs directory and configuration in place. As the container starts, it fails with the following:

2017-07-05 15:07:41,933+0000 INFO [FelixStartLevel] *SYSTEM org.sonatype.nexus.quartz.internal.QuartzSchedulerSPI - Quartz Scheduler v2.2.2 2017-07-05 15:07:42,454+0000 INFO [FelixStartLevel] *SYSTEM org.sonatype.nexus.quartz.internal.task.QuartzTaskInfo - Task 'Backup' [db.backup] : state=WAITING 2017-07-05 15:07:42,543+0000 INFO [FelixStartLevel] *SYSTEM org.sonatype.nexus.quartz.internal.task.QuartzTaskInfo - Task 'Storage facet cleanup' [repository.storage-facet-cleanup] : state=WAITING 2017-07-05 15:07:42,557+0000 INFO [FelixStartLevel] *SYSTEM org.sonatype.nexus.quartz.internal.task.QuartzTaskInfo - Task 'Rebuild' [repository.rebuild-index] : state=WAITING 2017-07-05 15:07:42,684+0000 ERROR [FelixStartLevel] *SYSTEM org.sonatype.nexus.repository.internal.blobstore.BlobStoreManagerImpl - Failed transition: NEW -> STARTED org.sonatype.nexus.blobstore.api.BlobStoreException: BlobId: null, Unable to initialize blob store directory structure: default at org.sonatype.nexus.blobstore.file.internal.FileBlobStore.init(FileBlobStore.java:584) [na:na] at org.sonatype.nexus.repository.internal.blobstore.BlobStoreManagerImpl.newBlobStore(BlobStoreManagerImpl.java:201) [na:na] at org.sonatype.nexus.repository.internal.blobstore.BlobStoreManagerImpl.doStart(BlobStoreManagerImpl.java:102) [na:na] at org.sonatype.nexus.common.stateguard.StateGuardLifecycleSupport.start(StateGuardLifecycleSupport.java:67) [org.sonatype.nexus.common:3.3.2.02] at org.sonatype.nexus.common.stateguard.MethodInvocationAction.run(MethodInvocationAction.java:39) [org.sonatype.nexus.common:3.3.2.02] at org.sonatype.nexus.common.stateguard.StateGuard$TransitionImpl.run(StateGuard.java:191) [org.sonatype.nexus.common:3.3.2.02] at org.sonatype.nexus.common.stateguard.TransitionsInterceptor.invoke(TransitionsInterceptor.java:56) [org.sonatype.nexus.common:3.3.2.02] at org.sonatype.nexus.repository.manager.internal.RepositoryManagerImpl.doStart(RepositoryManagerImpl.java:208) [na:na] at org.sonatype.nexus.common.stateguard.StateGuardLifecycleSupport.start(StateGuardLifecycleSupport.java:67) [org.sonatype.nexus.common:3.3.2.02] at org.sonatype.nexus.common.stateguard.MethodInvocationAction.run(MethodInvocationAction.java:39) [org.sonatype.nexus.common:3.3.2.02] at org.sonatype.nexus.common.stateguard.StateGuard$TransitionImpl.run(StateGuard.java:191) [org.sonatype.nexus.common:3.3.2.02] at org.sonatype.nexus.common.stateguard.TransitionsInterceptor.invoke(TransitionsInterceptor.java:56) [org.sonatype.nexus.common:3.3.2.02] at org.sonatype.nexus.extender.NexusLifecycleManager.startComponent(NexusLifecycleManager.java:153) [org.sonatype.nexus.extender:3.3.2.02] at org.sonatype.nexus.extender.NexusLifecycleManager.to(NexusLifecycleManager.java:93) [org.sonatype.nexus.extender:3.3.2.02] at org.sonatype.nexus.extender.NexusContextListener.frameworkEvent(NexusContextListener.java:188) [org.sonatype.nexus.extender:3.3.2.02] at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1429) [org.apache.felix.framework-5.6.1.jar:na] at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308) [org.apache.felix.framework-5.6.1.jar:na] at java.lang.Thread.run(Thread.java:748) [na:1.8.0_131] Caused by: java.nio.file.AccessDeniedException: /nexus-data/blobs/default at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84) [na:1.8.0_131] at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) [na:1.8.0_131] at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) [na:1.8.0_131] at sun.nio.fs.UnixFileSystemProvider.createDirectory(UnixFileSystemProvider.java:384) [na:1.8.0_131] at java.nio.file.Files.createDirectory(Files.java:674) [na:1.8.0_131] at java.nio.file.Files.createAndCheckIsDirectory(Files.java:781) [na:1.8.0_131] at java.nio.file.Files.createDirectories(Files.java:767) [na:1.8.0_131] at org.sonatype.nexus.common.io.DirectoryHelper.mkdir(DirectoryHelper.java:143) [na:na] at org.sonatype.nexus.blobstore.file.internal.FileBlobStore.init(FileBlobStore.java:579) [na:na] ... 17 common frames omitted

So far as I can tell it's expecting an empty or clean install default store in the blobs directory, but because I have an existing installation this fails. How is the container supposed to handle an existing persistent data volume?

$ docker logs -f nexus
2018-04-11 06:12:10,355+0000 INFO [jetty-main-1] org.sonatype.nexus.bootstrap.jetty.JettyServer - Running
2018-04-11 06:12:10,356+0000 ERROR [main] *SYSTEM org.sonatype.nexus.bootstrap.jetty.JettyServer - Start failed
java.lang.IllegalArgumentException: Bad temp directory: /tmp/JettyContext5630915593536410496
at org.eclipse.jetty.webapp.WebAppContext.setTempDirectory(WebAppContext.java:1119)
at org.eclipse.jetty.webapp.WebInfConfiguration.resolveTempDirectory(WebInfConfiguration.java:326)
at org.eclipse.jetty.webapp.WebInfConfiguration.preConfigure(WebInfConfiguration.java:68)
at org.eclipse.jetty.webapp.WebAppContext.preConfigure(WebAppContext.java:457)
at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:493)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95)
at org.eclipse.jetty.server.Server.doStart(Server.java:282)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
at org.sonatype.nexus.bootstrap.jetty.JettyServer$JettyMainThread.run(JettyServer.java:247)
Exception in thread "main" java.lang.IllegalArgumentException: Bad temp directory: /tmp/JettyContext5630915593536410496
at org.eclipse.jetty.webapp.WebAppContext.setTempDirectory(WebAppContext.java:1119)
at org.eclipse.jetty.webapp.WebInfConfiguration.resolveTempDirectory(WebInfConfiguration.java:326)
at org.eclipse.jetty.webapp.WebInfConfiguration.preConfigure(WebInfConfiguration.java:68)
at org.eclipse.jetty.webapp.WebAppContext.preConfigure(WebAppContext.java:457)
at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:493)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95)
at org.eclipse.jetty.server.Server.doStart(Server.java:282)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
at org.sonatype.nexus.bootstrap.jetty.JettyServer$JettyMainThread.run(JettyServer.java:247)

Hi there,

since I usually see a warning within the Nexus Repository Manager about the to low file descriptors value, I would like to ask that the Pull Request gets merged - Pretty please :-)

The Nexus documentation mentioned that the to low file descriptors value my cause loss of data :-(

Thank you very much!

Hi,

Can you provide a docker tag for Nexus 3 milestone 5.

I run docker using the following commands in the tutorial:

$ docker run -d --name nexus-data sonatype/nexus echo "data-only container for Nexus"
$ docker run -d -p 8081:8081 --name nexus --volumes-from nexus-data sonatype/nexus

but when I open http://127.0.0.1:8081/, I got 404 error.

Error text in browser

HTTP ERROR: 404
Problem accessing /. Reason:
Not Found
Powered by Jetty://

Following the description on https://hub.docker.com/r/sonatype/nexus/
{
docker pull sonatype/nexus:oss
docker run -d -p 8081:8081 --name nexus sonatype/nexus:oss
}
Provides me with a running container, but without a web gui to manage it at http://localhost:8081

Hi,

Why do you use this dockerfile/java:oracle-java7 version of Java image and not just the official build :

FROM java:7

?

Dear team
at first thanks a lot to share this work!
it is really great.

I would like to know if you could help me to modify your code to add p2 support to your nexus docker instance?
They are two plugins to install

https://books.sonatype.com/nexus-book/reference/p2-sect-intro.html
Nexus P2 Repository Plugin
Nexus P2 Bridge Plugin

Thanks

Francois from France

Given Nexus supports so many other binary repository formats (i.e.: NPM, NuGet, etc, in addition to Maven) was wondering if there was anything available yet to configure it as a potential storage repository for Docker images (private ones) like Docker Registry Hub, Google Container Repository, etc.

Following the description on https://hub.docker.com/r/sonatype/nexus/
{
docker pull sonatype/nexus:oss
docker run -d -p 8081:8081 --name nexus sonatype/nexus:oss
}
Provides me with a running container, but without a web gui to manage it at http://localhost:8081
Is a web server/gui included in the nexus container, and if so how can I configure this?

The next error has appeared every few days and Nexus server become unavailable:

300 WARN [quartz-9-thread-12] *SYSTEM org.sonatype.nexus.blobstore.file.FileBlobStore - Attempt to access non-existent blob 60cac04a-2ebb-48d8-a55c-a39306e28192 (/nexus-data/blobs/blob01/content/vol-18/chap-28/60cac04a-2ebb-48d8-a55c-a39306e28192.properties)
2021-07-24 22:15:12,616+0300 WARN

Hi all,
could you help to take a look at this? thanks.
I created a container with this image and downloaded the remote index of central rep, and then I exported the container to be a docker image and tired to imported it into another server. It supposed to work normal after I created a corresponding container, but two issues encountered:

1. the nexus failed to start and the log complaint no valid JVM existed.
   --- I fixed it
2. and then the nexus service succeeded to run, but it seemed that all the repositories lost the indexes I ever downloaded.

can the container be exported? Can user recreate an container base on the exported image?

Really appreciate your comments, thanks. : )

Our organization currently uses Nexus version Sonatype Nexus™ 2.5.1-01. We need to know if this version support as private repository of Docker Images and is there any official support as well.

Thanks,
Srinath

With mounted volume from host, it shows "java.io.IOException: No space left on device" error when running indexing to sync the remote index with local one.

The problem is that I have more than enough disk on the mounted volume while nexus running from inside the docker container does not think so.

pls help...

I just installed the "docker-nexus" following the documentation, by this command:

docker run -d -p 8081:8081 --name nexus sonatype/nexus:oss

Then I can open http://localhost:8081 from browser, and login to nexus successfully. But the problem is I can't find any docker related features.

I tried to add a new proxy repository, but there is no "docker" type as I expected:

Do I miss anything?

Hi all,

I'm currently exploring the use of a nexus repository that runs on Oracle Linux with a container host using Podman.

I have tried to install it according to the guide, but got the error "The host system is allocating a maximum of 2 cores to the application. A minimum of 4 is recommended." on the system check status.

I have tried to check the availability of the CPU in the container with the command

cat / proc / cpuinfo | awk '/ ^ processor / {print $ 3}' | toilet -l

The output generated by the CPU in the container is 6. Can you help with the configuration needed for the fixing issue above?

Regards,

Will this docker image be upgraded to support nexus 3?

If /sonatype-work volume is mounted from a dedicated data container :
sudo docker create --name nexus-data -v /var/lib/nexus:/sonatype-work busybox
sudo docker create --name nexus-server --volumes-from nexus-data sonatype/nexus

Container cannot start :
sudo docker start nexus-server

nexus-server_1 | 2016-06-24 10:28:41,298+0000 WARN [jetty-main-1] *SYSTEM org.sonatype.nexus.util.LockFile - Failed to write lock file
nexus-server_1 | java.io.FileNotFoundException: /sonatype-work/nexus.lock (Permission denied)

Data container, as the server container itself, must be created from sonatype/nexus docker image, what is weird IMO.
sudo docker create --name nexus-data -v /var/lib/nexus:/sonatype-work sonatype/nexus

As far as I know, Nexus is the only docker image which require such a constraint.