Accessing the Orient DB Console: Nexus as Docker Container

[RM]

Hello,

I am running into an issue where my Nexus won't start , i traced the problem to data corrupting in Orient DB

The instructions posted at https://support.sonatype.com/hc/en-us/articles/115002930827-Accessing-the-OrientDB-Console indicate how to connect to Orient DB

But the above instructions will only work when nexus runs on the same host where data directories are located.

In a docker container scenario, the jar exists within the container while the data directory and the java executable exist on the host.

Any pointers on accessing Orient DB Console when Nexus runs as a docker container with a host volume mount for data?

Thanks in advance for your guidance

Regards

[Rok Prodan]

Hello,

I don't have the answer to your question but we had plenty of issues with data corruption in Orient DB last month.
If you need any help with solving those I can help.

Meanwhile could you attach the snippet of Nexus application logs when the error occurs?

Kind regards,

Rok Prodan

--
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+unsubscribe@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/c36102a4-ea53-478a-8ba1-81e0303b51e0%40glists.sonatype.com.
For more options, visit https://groups.google.com/a/glists.sonatype.com/d/optout.

[Peter Lynch]

I mentioned this in the other thread, but... simply do a temporary unpack of Nexus in the host that can access the same data directory as the docker volume mount. Config the temp install to point at the data directory and launch the console with that install instead.

Thanks in advance for your guidance

Regards

[Bradley Beck]

If you normally run NXRM in a container with something like the following:

docker run -d -p 8081:8081 --name nexus -v /some/dir/nexus-data:/nexus-data sonatype/nexus3

Then you should be able to get access to the shell as follows and then follow the instructions in the KB article:

docker run -it -p 8081:8081 --name nexus -v /some/dir/nexus-data:/nexus-data sonatype/nexus3 /bin/bash

This is basically just running the same container with the same volume arguments but in interactive mode and telling it to start the shell instead of NXRM.

Hope that helps.

-Brad

--
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.

[RM]

Yes, i am going to try that. now.

Simple but great suggestion, thanks a lot.