Nexus Docker Image Failing to Start on Existing Datastore

[James Renaud]

Hey folks,

Here's my setup:

- Nexus 3 docker image running on an AWS EC2 image

- Existing data on an NFS store (configuration, and blob storage)

When the docker comes up and is performing its initial install, it appears as though it is attempting to initialise the blob storage, but fails with the following stack message:

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

I'm not sure how Nexus is supposed to handle existing storage, has anyone run into this before?

Thanks for any guidance!

Cheers,

James.

[James Renaud]

Turns out this was permissions related and I missed in the logs the following:

Caused by: java.nio.file.AccessDeniedException: /nexus-data/blobs/apt-mitel/content

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]

It appears when I restored the blobs folder, ownership was not applied recursively to UID 200 which was causing issues. Doing a simple chown -R 200:200 blobs/ resolved this problem.