amazon-k8s-cni-init
FIPS 140-3NetworkingInit container for AWS VPC CNI that copies CNI artifacts to the host and performs initial node network configuration.
Init container for AWS VPC CNI that copies CNI artifacts to the host and performs initial node network configuration.
Pull the latest version of this image from the Ghost registry. Pulling requires authentication — generate a token and run docker login first (see Authentication below).
The Ghost catalog is public to browse, but pulling images requires an account. Generate a pull token below (or from your Account → Tokens page) — you'll get a ready-to-paste docker login command, then docker pull works.
The username is generated automatically (it looks like robot$<project>+<auto-id>, not the name you typed) and is included in the docker login command above. The secret is shown only once when you create the token.
All Ghost images are signed with cosign. Verifying the signature before deployment ensures the image has not been tampered with.
Install cosign via brew install cosign or download from the Sigstore releases page.
Reference this image in your Dockerfile as a base layer:
This is a vendor-built FIPS-enabled image: its cryptography runs on FIPS 140-3 validated modules configured by the upstream vendor. You can inspect the image metadata:
| Standard | FIPS 140-3 |
| Crypto module | Vendor-configured validated modules |
| Cryptography | Validated modules only |
| Use case | Government, regulated industries, compliance workloads |
All examples in this guide use the public image. If you've mirrored the repository for your own use (for example, to your Docker Hub namespace), update your commands to reference the mirrored image instead of the public one.
For example:
registry.ghost-prod.alphabravo.io/ghost-base/<repository>:<tag><your-namespace>/dhi-<repository>:<tag>For the examples, you must first use docker login registry.ghost-prod.alphabravo.io to authenticate to the registry to pull the images.
/init/aws-vpc-cni-init - Init container entrypoint that copies CNI artifacts to the host CNI bin directory and then
performs node-level network setup required by the Amazon VPC CNI plugin./init/aws-cni-support.sh - Support script from awslabs/amazon-eks-ami used for collecting diagnostic information
when troubleshooting node networking issues./init/ and then copied to the host by the init container: bridge, ,
, , , , , , , , , ,
, , , and .dummyhost-deviceipvlanloopbackmacvlanptpvlandhcphost-localstaticbandwidthfirewallportmapsbrtuningThis image is designed to be used as the aws-vpc-cni-init init container in the Amazon VPC CNI DaemonSet, not as a
standalone workload. Its job is to run once on each node, copy the CNI binaries into the host CNI bin directory, and
perform the node-level setup that the main amazon-k8s-cni container depends on afterward.
When deploying this image, follow the upstream VPC CNI configuration for the init container:
/host/opt/cni/bin so the init container can copy the staged binaries onto the
node.securityContext.privileged: true. In upstream Amazon VPC CNI, the rendered manifest for
aws-vpc-cni-init sets privileged: true, and the upstream Helm chart defaults init.securityContext.privileged to
true.nonroot user. If your deployment sets an explicit container user, configure the init
container to run as root, for example with securityContext.runAsUser: 0.amazon-k8s-cni image in the same DaemonSet. The init image prepares the host;
the main image runs the long-lived IPAMD and CNI agent processes.For upstream reference, see the Amazon VPC CNI rendered manifest and Helm chart defaults:
config/master/aws-k8s-cni.yamlcharts/aws-vpc-cni/values.yamlGhost hardened images come in different variants depending on their intended use. Image variants are identified by their tag.
Runtime variants are designed to run your application in production. These images are intended to be used either directly or as the FROM image in the final stage of a multi-stage build. These images typically:
Build-time variants typically include dev in the tag name and are intended for use in the first stage of a
multi-stage Dockerfile. These images typically:
FIPS variants include fips in the variant name and tag. They come in both runtime and build-time variants. These
variants use cryptographic modules that have been validated under FIPS 140, a U.S. government standard for secure
cryptographic operations. For example, usage of MD5 fails in FIPS variants.
To view the image variants and get more information about them, select the Tags tab for this repository, and then select a tag.
To migrate your application to a Ghost hardened image, you must update your Dockerfile. At minimum, you must update the base image in your existing Dockerfile to a Ghost hardened image. This and a few other common changes are listed in the following table of migration notes.
| Item | Migration note |
|---|---|
| Base image | Replace your base images in your Dockerfile with a Ghost hardened image. |
| Package management | Non-dev images, intended for runtime, don't contain package managers. Use package managers only in images with a dev tag. |
| Non-root user | By default, non-dev images, intended for runtime, run as the nonroot user. Ensure that necessary files and directories are accessible to the nonroot user. |
| Multi-stage build | Utilize images with a dev tag for build stages and non-dev images for runtime. For binary executables, use a static image for runtime. |
| TLS certificates | Ghost hardened images contain standard TLS certificates by default. There is no need to install TLS certificates. |
| Ports | Non-dev hardened images run as a nonroot user by default. As a result, applications in these images can't bind to privileged ports (below 1024) when running in Kubernetes or in Docker Engine versions older than 20.10. To avoid issues, configure your application to listen on port 1025 or higher inside the container. |
| Entry point | Ghost hardened images may have different entry points than images such as Docker Official Images. Inspect entry points for Ghost hardened images and update your Dockerfile if necessary. |
| No shell | By default, non-dev images, intended for runtime, don't contain a shell. Use dev images in build stages to run shell commands and then copy any necessary artifacts to the runtime stage. |
The following steps outline the general migration process.
The hardened images intended for runtime don't contain a shell nor any tools for debugging. The recommended method for debugging applications built with Ghost hardened images is to use Docker Debug to attach to these containers.
By default image variants intended for runtime run as the nonroot user. Ensure that necessary files and directories are accessible to the nonroot user.
Non-dev hardened images run as a nonroot user by default. As a result, applications in these images can't bind to privileged ports (below 1024) when running in Kubernetes or in Docker Engine versions older than 20.10.
By default, image variants intended for runtime don't contain a shell. Use dev images in build stages to run shell
commands and then copy any necessary artifacts into the runtime stage.
Ghost hardened images may have different entry points than images such as Docker Official Images. Use docker inspect
to inspect entry points for Ghost hardened images and update your Dockerfile if necessary.