Chainguard Container for nacos

Dynamic service discovery, configuration and service management platform for building AI cloud native applications.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/nacos:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

The nacos image is compatible with the upstream nacos/nacos-server image with the following differences:

• The image runs as a non-root user
• Uses Wolfi packages for improved security
• Contains minimal dependencies for reduced attack surface

There are no breaking changes in the API or configuration.

Getting Started

The nacos image can be run in standalone or cluster mode. For development and testing, standalone mode is recommended:

docker run -d --name nacos \
  -e MODE=standalone \
  -e NACOS_AUTH_ENABLE=false \
  -p 8848:8848 \
  cgr.dev/ORGANIZATION/nacos

After starting, the Nacos console will be available at http://localhost:8848/nacos. The default credentials are nacos/nacos.

For production deployments, enable authentication and use cluster mode:

docker run -d --name nacos \
  -e MODE=cluster \
  -e NACOS_AUTH_ENABLE=true \
  -e NACOS_AUTH_TOKEN=your-secret-token \
  -e NACOS_AUTH_IDENTITY_KEY=serverIdentity \
  -e NACOS_AUTH_IDENTITY_VALUE=security \
  -p 8848:8848 \
  cgr.dev/ORGANIZATION/nacos

Usage with Helm

To deploy Nacos on Kubernetes using Helm:

helm repo add ygqygq2 https://ygqygq2.github.io/charts
helm repo update

cat > values.yaml <<EOF
image:
  registry: cgr.dev/ORGANIZATION
  repository: nacos
  tag: latest

nacos:
  serverMode: standalone
  domainName: nacos.example.com
EOF

helm install nacos ygqygq2/nacos -f values.yaml

Configuration

Nacos can be configured through environment variables. Key configuration options include:

• MODE: Set to standalone for single-node deployment or cluster for multi-node
• NACOS_AUTH_ENABLE: Enable authentication (recommended for production)
• NACOS_AUTH_TOKEN: JWT token for authentication (base64 encoded)
• SPRING_DATASOURCE_PLATFORM: Database type (mysql for external database)
• MYSQL_SERVICE_HOST: MySQL host when using external database
• MYSQL_SERVICE_DB_NAME: Database name for MySQL

For a complete list of configuration options, refer to the Nacos documentation.

Documentation and Resources

• Nacos Official Documentation
• Nacos Quick Start Guide
• Nacos Docker Hub
• Helm Chart Repository

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.