DirectorySecurity AdvisoriesPricing
Sign in
Directory
nacos logo

nacos

packaged by Chainguard

Last changed
Request a free trial

Contact our team to test out this image for free. Please also indicate any other images you would like to evaluate.

Tags
Overview
Comparison
Provenance
Specifications
SBOM
Vulnerabilities
Advisories

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

Chainguard's nacos image is comparable to the upstream nacos/nacos-server image. It uses the same docker-startup.sh entrypoint and environment variables, so existing configurations carry over. It differs from the upstream image in the following ways:

  • The image runs as the non-root nonroot user (UID 65532) instead of root.
  • The image does not include the Python skill-scanner tool or the skills-data.zip and agentspec-data.zip seed archives that the upstream image bundles for the Nacos AI registry.

Prerequisites

The examples below use Docker, curl, jq, and openssl. The Helm example also needs a Kubernetes cluster, kubectl, and helm.

Getting Started

Nacos 3.x enables authentication by default. Before the server starts, the container requires a Base64-encoded token secret of at least 32 bytes, plus a server identity key and value that Nacos servers use to authenticate to each other. Generate the secrets and start a standalone server, which stores its data in an embedded Derby database:

export NACOS_AUTH_TOKEN="$(openssl rand -base64 32)"
export NACOS_AUTH_IDENTITY_VALUE="$(openssl rand -hex 16)"

docker run -d --name nacos \
  -e MODE=standalone \
  -e NACOS_AUTH_TOKEN \
  -e NACOS_AUTH_IDENTITY_KEY=serverIdentity \
  -e NACOS_AUTH_IDENTITY_VALUE \
  -p 8080:8080 \
  -p 8848:8848 \
  -p 9848:9848 \
  cgr.dev/ORGANIZATION/nacos:latest

Port 8848 serves the HTTP API, port 9848 serves the gRPC API that Nacos client SDKs use, and port 8080 serves the web console. The readiness endpoint answers with HTTP 200 while the server is still starting, so wait until its response reports ok:

until curl -s http://localhost:8848/nacos/v3/admin/core/state/readiness | grep -q '"data":"ok"'; do sleep 2; done

Nacos 3.x has no default password. Set the password of the nacos administrator, then log in to get an access token:

curl -s -X POST http://localhost:8848/nacos/v3/auth/user/admin -d 'password=ChangeMe-2026' | jq -c .
TOKEN="$(curl -s -X POST http://localhost:8848/nacos/v3/auth/user/login \
  -d 'username=nacos&password=ChangeMe-2026' | jq -r .accessToken)"
{"code":0,"data":{"password":"ChangeMe-2026","username":"nacos"},"message":"success"}

Publish a configuration and read it back:

curl -s -X POST http://localhost:8848/nacos/v3/admin/cs/config -H "accessToken: $TOKEN" \
  -d 'dataId=app.properties&groupName=DEFAULT_GROUP&type=properties&content=greeting=hello' | jq -c .
curl -s "http://localhost:8848/nacos/v3/admin/cs/config?dataId=app.properties&groupName=DEFAULT_GROUP" \
  -H "accessToken: $TOKEN" | jq -r .data.content
{"code":0,"data":true,"message":"success"}
greeting=hello

The web console is available at localhost:8080. Log in as nacos with the password you set.

Deploy with Helm

The community ygqygq2/nacos Helm chart works with this image. Store the authentication secrets in a Kubernetes Secret:

kubectl create secret generic nacos-auth \
  --from-literal=NACOS_AUTH_TOKEN="$(openssl rand -base64 32)" \
  --from-literal=NACOS_AUTH_IDENTITY_KEY=serverIdentity \
  --from-literal=NACOS_AUTH_IDENTITY_VALUE="$(openssl rand -hex 16)"

Then install a standalone server. The values below disable the chart's bundled MySQL, replace the chart's default environment variables (which include a sample token) with the Secret, and mount only the data and logs directories, because the chart's default mounts also cover /home/nacos/plugins:

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

mode: standalone

mysql:
  enabled: false
initDB:
  enabled: false

extraEnvVars:
  - name: MODE
    value: standalone
extraEnvVarsSecret: nacos-auth

persistence:
  mountPaths:
    - name: data-storage
      mountPath: /home/nacos/data
      subPath: data
    - name: data-storage
      mountPath: /home/nacos/logs
      subPath: logs
EOF

helm install nacos ygqygq2/nacos --values values.yaml --wait --timeout 10m

To reach the server from your machine, forward its ports in a separate terminal, then run the administrator and configuration commands from the previous section:

kubectl port-forward svc/nacos 8848:8848 8080:8080

Configuration

The embedded Derby database suits development and single-node use. For production, and for cluster mode, Nacos stores its data in MySQL. The following example runs Nacos against Chainguard's mysql image.

As with the upstream image, initialize the database with the Nacos schema before the first start. Extract the schema that matches the server version from the nacos image, and let MySQL load it on first start through /docker-entrypoint-initdb.d:

docker rm -f nacos
docker network create nacos

docker run --rm --entrypoint cat cgr.dev/ORGANIZATION/nacos:latest conf/mysql-schema.sql > nacos-mysql-schema.sql

docker run -d --name nacos-mysql --network nacos \
  -e MYSQL_ROOT_PASSWORD=change-me-root \
  -e MYSQL_DATABASE=nacos \
  -e MYSQL_USER=nacos \
  -e MYSQL_PASSWORD=change-me \
  -v "$PWD/nacos-mysql-schema.sql:/docker-entrypoint-initdb.d/nacos-mysql-schema.sql:ro" \
  cgr.dev/ORGANIZATION/mysql:8.4

until docker logs nacos-mysql 2>&1 | grep -q 'port: 3306'; do sleep 2; done

Then start Nacos with the MySQL connection settings. SPRING_DATASOURCE_PLATFORM selects the MySQL datasource plugin, and MYSQL_SERVICE_DB_PARAM adds allowPublicKeyRetrieval=true to the default JDBC parameters, because MySQL 8.4 authenticates with caching_sha2_password, which needs it when SSL is off:

docker run -d --name nacos --network nacos \
  -e MODE=standalone \
  -e SPRING_DATASOURCE_PLATFORM=mysql \
  -e MYSQL_SERVICE_HOST=nacos-mysql \
  -e MYSQL_SERVICE_DB_NAME=nacos \
  -e MYSQL_SERVICE_USER=nacos \
  -e MYSQL_SERVICE_PASSWORD=change-me \
  -e MYSQL_SERVICE_DB_PARAM='characterEncoding=utf8&connectTimeout=1000&socketTimeout=3000&autoReconnect=true&useSSL=false&allowPublicKeyRetrieval=true' \
  -e NACOS_AUTH_TOKEN \
  -e NACOS_AUTH_IDENTITY_KEY=serverIdentity \
  -e NACOS_AUTH_IDENTITY_VALUE \
  -p 8080:8080 \
  -p 8848:8848 \
  -p 9848:9848 \
  cgr.dev/ORGANIZATION/nacos:latest

After repeating the readiness, administrator, and configuration commands from Getting Started, the configuration is stored in MySQL:

docker exec -e MYSQL_PWD=change-me nacos-mysql mysql -unacos nacos \
  -e "SELECT data_id, content FROM config_info WHERE data_id = 'app.properties'"
data_id	content
app.properties	greeting=hello

To run a cluster, set MODE=cluster and list every member in NACOS_SERVERS (for example, nacos-1:8848 nacos-2:8848 nacos-3:8848), and point all members at the same database. Refer to the Nacos cluster deployment guide for details.

Documentation and Resources

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:

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.

Licenses

Chainguard's container images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" tag of this image:

    For a complete list of licenses, please refer to this Image's SBOM.

    Software license agreement

    Compliance

    Chainguard Containers are SLSA Level 3 compliant with detailed metadata and documentation about how it was built. We generate build provenance and a Software Bill of Materials (SBOM) for each release, with complete visibility into the software supply chain.

    SLSA compliance at Chainguard

    This image helps reduce time and effort in establishing PCI DSS 4.0 compliance with low-to-no CVEs.

    PCI DSS at Chainguard

    Category
    Application

    The trusted source for open source

    Talk to an expert
    PrivacyTerms

    Product

    Chainguard ContainersChainguard LibrariesChainguard VMsChainguard OS PackagesChainguard ActionsChainguard Agent SkillsIntegrationsPricing
    © 2026 Chainguard, Inc. All Rights Reserved.
    Chainguard® and the Chainguard logo are registered trademarks of Chainguard, Inc. in the United States and/or other countries.
    The other respective trademarks mentioned on this page are owned by the respective companies and use of them does not imply any affiliation or endorsement.