Updated JRE and reduced custom config #51
Conversation
bradbeck
force-pushed
the
update-jre-and-config-cleanup
branch
from
1f04ac8
to
7a6fa3c
Compare
|
+1, tested and seems to work fine |
|
+1 |
| NEXUS_DATA=/nexus-data \ | ||
| NEXUS_CONTEXT='' | ||
| NEXUS_CONTEXT='' \ | ||
| SONATYPE_WORK=${SONATYPE_DIR}/sonatype-work |
There was a problem hiding this comment.
is this right? I would expect this to be in NEXUS_DATA and not within the NEXUS_HOME dir, unless I'm misunderstanding?
There was a problem hiding this comment.
I believe the idea is to leave KARAF_DATA configured as ../sonatype-work/nexus3 and instead symlink ${NEXUS_DATA} as ${SONATYPE_WORK}/nexus3 - rather than change KARAF_DATA which involves updating several entries in nexus.vmoptions (because that file doesn't support property interpolation).
If install4j ever added property interpolation to nexus.vmoptions that would avoid the need to update entries to reflect the new property value, but for now we either need to edit it wholesale or take Brad's symlink approach.
There was a problem hiding this comment.
@kellyrob99 Note SONATYPE_WORK is effectively /opt/sonatype/sonatype-work and is not within NEXUS_HOME which is effectively /opt/sonatype/nexus.
|
+1 |
|
|
||
| RUN useradd -r -u 200 -m -c "nexus role account" -d ${NEXUS_DATA} -s /bin/false nexus \ | ||
| && mkdir -p ${NEXUS_DATA}/etc ${NEXUS_DATA}/log ${NEXUS_DATA}/tmp ${SONATYPE_WORK} \ | ||
| && ln -s ${NEXUS_DATA} ${SONATYPE_WORK}/nexus3 \ |
There was a problem hiding this comment.
This symlink means that data is written to /opt/sonatype/sonatype-work/nexus3. I believe this forces users to have a docker volume at /opt/sonatype/sonatype-work rather than /nexus-data like the docs suggest. Is this intentional?
There was a problem hiding this comment.
You can still use /nexus-data:
docker run -v /some/local/dir:/nexus-data sonatype/nexus3
There was a problem hiding this comment.
@Wilfred Out of the box NXRM writes to /sonatype-work/nexus3. I believe the link has the inverse affect you're suggesting. It's taking stuff from where we write by default and putting into ${NEXUS_DATA}. I defer to the author however.
Updated to the latest JRE. Reduced the custom configuration while maintaining the
/nexus-datavolume.