packaged by Chainguard
Contact our team to test out this image for free. Please also indicate any other images you would like to evaluate.
Container registry adapters to work with NeuVector vulnerability scan
Chainguard Containers are regularly-updated, secure-by-default container images.
For those with access, this container image is available on cgr.dev:
Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.
Chainguard's neuvector-registry-adapter image is comparable to the upstream neuvector/registry-adapter image. It runs the same /usr/local/bin/adapter entrypoint from the / working directory and reads the same environment variables, so the NeuVector core Helm chart deploys it without other changes.
The one difference is the user. The upstream image runs as root, while this image runs as the nonroot user 65532, which limits what a compromised adapter can do in the container. The adapter writes certificates to two directories, and the image makes both of them owned by that user:
/etc/neuvector/certs, where it generates a self-signed HTTPS certificate when none is mounted./etc/neuvector/certs/internal, where it stores the internal certificates when the chart sets AUTO_INTERNAL_CERT.The core chart sets a pod security context only when cve.adapter.runAsUser is set, so the adapter runs as 65532 by default. With the chart's default certificate settings, the HTTPS certificate is mounted from a Secret and the internal certificates go to an emptyDir volume, so a different cve.adapter.runAsUser works as well.
The registry adapter implements the Harbor Pluggable Scanner API. Harbor calls the adapter's scanner endpoints with HTTP basic authentication, and the adapter forwards each scan request over gRPC to the NeuVector controller. It ships as an optional component of the NeuVector core Helm chart and starts serving the Harbor API only after it connects to a controller, so deploy it together with the rest of NeuVector.
Add the NeuVector Helm repository:
Create the namespace and the Secret holding the credentials Harbor uses to call the adapter, replacing HARBOR_PASSWORD with a password of your choice:
The chart builds the controller, enforcer, manager, and adapter image references from one top-level registry value, so a values file that points the adapter at cgr.dev points those components there too. The following values file uses Chainguard images for every NeuVector component and enables the adapter:
Install the chart with it:
Wait for the adapter to roll out:
The chart exposes the adapter through the neuvector-service-registry-adapter Service on port 9443. To scan images pushed to Harbor with NeuVector, add a scanner under Interrogation Services in Harbor with the endpoint https://neuvector-service-registry-adapter.neuvector:9443/endpoint, the harbor user name, and the password from the harbor-auth Secret.
The chart configures the adapter through environment variables. It sets CLUSTER_JOIN_ADDR to the controller Service, HARBOR_SERVER_PROTO from cve.adapter.harbor.protocol, and HARBOR_BASIC_AUTH_USERNAME and HARBOR_BASIC_AUTH_PASSWORD from the Secret named by cve.adapter.harbor.secretName. With https the adapter listens on port 9443, and with http on port 8090.
By default the adapter serves HTTPS with a certificate the chart generates, which Harbor cannot verify. To have Harbor verify the adapter, serve a certificate issued for the adapter's Service name instead. Store the certificate and key in a TLS Secret, replacing tls.crt and tls.key with your own files:
Then point the chart at the Secret in a second values file:
Apply both values files:
The chart mounts the Secret's files as /etc/neuvector/certs/ssl-cert.pem and /etc/neuvector/certs/ssl-cert.key, and the adapter uses them instead of generating its own certificate.
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.
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.
Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.
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.
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 agreementChainguard 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 ChainguardThis image helps reduce time and effort in establishing PCI DSS 4.0 compliance with low-to-no CVEs.
PCI DSS at ChainguardA FIPS validated version of this image is available for FedRAMP compliance. STIG is included with FIPS image.