Native Shell
Native Shell:AI 生成的 UI,在你的應用中原生呈現,涵蓋每個平台。iOS、Android、macOS、Windows 與 Linux 上的應用、GPUI 應用與網頁在執行時載入已簽名、沙箱隔離的 TSX 模組並繪製 th
AI 翻譯
Dockerized version of Nexus Repo Manager 3
翻譯準備中
開發工具Java · ShellGitHub @sonatype自行安裝營運者未確認
試用過了嗎? 點一下就好,不需要登入。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
安裝型專案無需部署網域也可驗證。個人儲存庫可透過 GitHub 登入驗證,組織儲存庫可使用上方的儲存庫驗證檔案。
製作者的介紹僅有上面的一句話。 更多詳情請閱讀儲存庫 README。 儲存庫 README ↗
正在載入完整 README。
檢視完整 README ↗Sonatype Nexus Repository is the single source of truth for all your internal and third-party binaries, components, and packages. Integrate all your development tools into a centralized binary repository manager so that you can choose the best open source components, optimize your build performance, and ship code quickly while increasing visibility across your SDLC.
As of version 3.77.0, the free edition of Nexus Repository is now called Sonatype Nexus Repository Community Edition.
Community Edition is designed to deliver robust repository management for individual users and small teams. Upgrading to 3.77.0 unlocks powerful new features, including access to previously Pro-only formats, seamless integration with containerized environments like Kubernetes, and more. Community Edition does also include some usage limitations. To learn more, see the Community Edition documentation.
Go read our contribution guidelines to get a bit more familiar with how we would like things to flow.
To run, binding the exposed port 8081 to the host, use:
docker run -d -p 8081:8081 --name nexus sonatype/nexus3
Note: As of version 3.91.0, the default sonatype/nexus3 image is based on Alpine Linux. See the Alpine Image section below for more details. A UBI-based variant is also available using the -ubi tag suffix.
When stopping, be sure to allow sufficient time for the databases to fully shut down.
docker stop --time=120 <CONTAINER_NAME>
To test:
curl http://localhost:8081/
To build the UBI-based image from Dockerfile.java21 you can use this command:
docker build --rm=true --tag=sonatype/nexus3 -f Dockerfile.java21 .
To build the Alpine-based image, use Dockerfile.alpine.java21 instead:
docker build --rm=true --tag=sonatype/nexus3 -f Dockerfile.alpine.java21 .
The following optional variables can be used when building the image:
NEXUS_VERSION to download from SonatypeNEXUS_VERSION
or NEXUS_DOWNLOAD_URL is providedChef Solo is used to build out the runtime and application layers of the Docker image. The Chef cookbook being used is available on GitHub at sonatype/chef-nexus-repository-manager.
A Red Hat certified container image can be created using Dockerfile.rh.ubi.java21 which is built to be compliant with Red Hat certification. The image includes additional meta data to comform with Kubernetes and OpenShift standards, a directory with the licenses applicable to the software and a man file for help on how to use the software. It also uses an ENTRYPOINT script the ensure the running user has access to the appropriate permissions for OpenShift 'restricted' SCC.
The Red Hat certified container image is available from the Red Hat Container Catalog and qualified accounts can pull it from registry.connect.redhat.com.
In addition to the Universal Base Image, we can build images based on:
As of version 3.91.0, the Alpine-based image is the default for Sonatype Nexus Repository.
The Alpine-based container image can be created using Dockerfile.alpine.java21. This Dockerfile is built to leverage the minimalistic and efficient nature of Alpine Linux, emphasizing fewer dependencies to achieve a cleaner SBOM (Software Bill of Materials) and a stronger security posture.
The Alpine-based container image includes minimal dependencies and uses an ENTRYPOINT script to ensure the application runs with the necessary permissions. It is optimized for rapid deployment and efficient resource usage.
The Alpine-based container image is available from Docker Hub and can be pulled using the following tags:
sonatype/nexus3:latest - Latest Alpine-based release (runs Java 21)sonatype/nexus3:3.XX.y - Specific version, Alpine-based (runs Java 21)sonatype/nexus3:3.XX.y-alpine - Explicit Alpine tag (runs Java 21)For users who prefer Red Hat Universal Base Image (UBI), a UBI-based variant is available using the -ubi tag suffix:
sonatype/nexus3:3.XX.y-ubi - Specific version, UBI-based (runs Java 21)The UBI-based container image can be created using Dockerfile.java21.
Our system requirements should be taken into account when provisioning the Docker container.
Default user is admin and the uniquely generated password can be found in the admin.password file inside the volume. See Persistent Data for information about the volume.
It can take some time (2-3 minutes) for the service to launch in a new container. You can tail the log to determine once Nexus is ready:
docker logs -f nexus
Installation of Nexus is to /opt/sonatype/nexus.
A persistent directory, /nexus-data, is used for configuration,
logs, and storage. This directory needs to be writable by the Nexus
process, which runs as UID 200.
There is an environment variable that is being used to pass JVM arguments to the startup script
INSTALL4J_ADD_VM_PARAMS, passed to the Install4J startup script. Defaults to -Djava.util.prefs.userRoot=${NEXUS_DATA}/javaprefs.This can be adjusted at runtime:
docker run -d -p 8081:8081 --name nexus -e INSTALL4J_ADD_VM_PARAMS="-Xms2703m -Xmx2703m -XX:MaxDirectMemorySize=2703m -Djava.util.prefs.userRoot=/some-other-dir" sonatype/nexus3
Java Memory Configuration Parameters:
The example above demonstrates configuring Java memory parameters. Each parameter controls a specific aspect of memory allocation:
-Xms2703m: Sets the initial heap size to 2703 MB-Xmx2703m: Sets the maximum heap size to 2703 MB-XX:MaxDirectMemorySize=2703m: Sets the maximum direct memory size to 2703 MBThese values should be adjusted based on your memory requirements. Setting -Xms and -Xmx to the same value prevents heap resizing and provides more predictable performance.
Of particular note, -Djava.util.prefs.userRoot=/some-other-dir can be set to a persistent path, which will maintain
the installed Sonatype Nexus Repository License if the container is restarted.
Another environment variable can be used to control the Nexus Context Path
NEXUS_CONTEXT, defaults to /This can be supplied at runtime:
docker run -d -p 8081:8081 --name nexus -e NEXUS_CONTEXT=nexus sonatype/nexus3
There are two general approaches to handling persistent storage requirements with Docker. See Managing Data in Containers for additional information.
docker volume create --name nexus-data
docker run -d -p 8081:8081 --name nexus -v nexus-data:/nexus-data sonatype/nexus3
mkdir /some/dir/nexus-data && chown -R 200 /some/dir/nexus-data
docker run -d -p 8081:8081 --name nexus -v /some/dir/nexus-data:/nexus-data sonatype/nexus3
If you are using Nexus Repository Core or Community Edition and need to report an issue or request an enhancement, open an issue here.
For help with Nexus Repository Core or Community Edition, please join the Sonatype Community to get tips and tricks from other users.
To report a security vulnerability, please see https://www.sonatype.com/report-a-security-vulnerability
Sonatype Nexus Repository Pro customers can contact our world-class support team at https://support.sonatype.com/.
Sonatype Nexus Repository Core is distributed with Sencha Ext JS pursuant to a FLOSS Exception agreed upon between Sonatype, Inc. and Sencha Inc. Sencha Ext JS is licensed under GPL v3 and cannot be redistributed as part of a closed source work.
All use of and access to Sonatype Nexus Repository Community Edition is governed by these terms and conditions.
Copyright © 2008-present Sonatype, Inc.