nuclio-dashboard-fips

packaged by Chainguard

Chainguard Container for nuclio-dashboard-fips

FIPS-enabled web dashboard and API for managing Nuclio serverless projects, functions, and API gateways, served with nginx.

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/nuclio-dashboard-fips: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 nuclio-dashboard-fips image packages the upstream Nuclio dashboard with its nginx frontend, startup scripts, Docker client, and Git client. It preserves the upstream entrypoint and command and runs as root, with nginx workers using the nginx account.

The web UI and API listen on port 8070; readiness (/ready) and liveness (/live) endpoints listen on port 8082. Configure health probes explicitly; this image does not include the upstream Docker uhttpc healthcheck.

The image includes an offline templates archive at /usr/share/nuclio-dashboard/templates.zip, also linked at /tmp/templates.zip, the upstream image's path and the upstream Helm chart's default. Frontend assets are built in the package; Node.js is not required at runtime.

This variant uses the FIPS-enabled dashboard and Docker client packages, with the hardened OpenSSL configuration for nginx.

FIPS Support

This Chainguard Container ships with a validated redistribution of OpenSSL's FIPS provider module. No configuration is required to enable FIPS mode. The dashboard and Docker client use Chainguard's FIPS Go toolchain, whose preferred cryptographic backend is the system OpenSSL library. If the OpenSSL provider cannot be loaded, the toolchain can fall back to the embedded, validated Go FIPS module. The hardened OpenSSL configuration also applies to nginx. For more on FIPS support and verification, consult the guide on FIPS-enabled Chainguard Containers on Chainguard Academy.

To display the dashboard binary's selected cryptographic backend without changing its selection policy, enable diagnostic output:

docker run --rm --entrypoint /usr/bin/dashboard \
  --env GODEBUG=cgr_verbose=1 \
  cgr.dev/ORGANIZATION/nuclio-dashboard-fips:latest --help

The diagnostic identifies OpenSSL or the embedded Go FIPS module. This command overrides the multi-process entrypoint to inspect the dashboard binary directly. To verify the bundled OpenSSL FIPS provider separately, run its self-test:

docker run --rm --entrypoint openssl-fips-test \
  cgr.dev/ORGANIZATION/nuclio-dashboard-fips:latest

Prerequisites

For local Docker deployment, the dashboard needs access to a Docker daemon to manage functions. Mounting the Docker socket grants the dashboard control of that daemon. For Kubernetes deployment, use the upstream Nuclio Helm chart and configure registry authentication.

Getting Started

Run the dashboard against a local Docker daemon, mapping container port 8070 to host port 8071:

docker run --detach --name nuclio-dashboard-fips \
  --publish 127.0.0.1:8071:8070 \
  --volume /var/run/docker.sock:/var/run/docker.sock \
  --tmpfs /etc/nuclio/dashboard/registry-credentials \
  cgr.dev/ORGANIZATION/nuclio-dashboard-fips:latest

Open http://localhost:8071/welcome to view the dashboard. The empty credentials directory avoids a startup warning when no private function registry credentials are supplied.

On hosts without network access, add --env NUCLIO_DASHBOARD_OFFLINE=true before the image reference. This enables Nuclio's offline function-build mode and prevents automatic base-image pulls, so preload the required build images and dependencies first. Template sources are configured separately through the archive or Git settings; this setting does not change the packaged templates archive.

To deploy on Kubernetes, create a values file that selects the dashboard and controller images and uses Kaniko for function builds:

cat > values.yaml <<'EOF'
controller:
  image:
    repository: cgr.dev/ORGANIZATION/nuclio-controller-fips
    tag: latest
dashboard:
  image:
    repository: cgr.dev/ORGANIZATION/nuclio-dashboard-fips
    tag: latest
  containerBuilderKind: kaniko
EOF

helm repo add nuclio https://nuclio.github.io/nuclio/charts
helm repo update
helm install nuclio nuclio/nuclio \
  --create-namespace --namespace nuclio --values values.yaml
kubectl --namespace nuclio port-forward service/nuclio-dashboard 8070:8070

Replace ORGANIZATION with your registry organization and configure its image pull credentials before installing. Open http://localhost:8070/welcome after port forwarding starts. Function builds also require access to a container registry; see the upstream registry configuration guide.

Documentation and Resources

• Nuclio documentation
• Nuclio Docker deployment
• Nuclio Kubernetes deployment

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.