istioctl
FIPS 140-3Monitoring & observabilityIstioctl image for managing Istio deployments
Istioctl image for managing Istio deployments
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.
The Istioctl image provides the istoctl binary for managing Istio installations. It is designed as a client-side CLI
tool.
Replace <tag> with the image variant you want to use.
kubectl run istioctl --image=registry.ghost-prod.alphabravo.io/ghost-base/istioctl:<tag> \
--rm -it --restart=Never -- --help
Use istioctl to generate Istio manifests for review before installation:
kubectl run istioctl --image=registry.ghost-prod.alphabravo.io/ghost-base/istioctl:<tag> \
--rm -it --restart=Never -- manifest generate
Key differences specific to the Istioctl DHI:
Ghost hardened images come in different variants depending on their intended use. Runtime variants run as a nonroot user without a shell or package manager.
To view the image variants and get more information about them, select the Tags tab for this repository.
To migrate to the Docker Hardened Istioctl image, update your image references:
image: registry.ghost-prod.alphabravo.io/ghost-base/istioctl:<tag>
The following are common issues that you may encounter during migration.
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. Docker Debug provides a shell, common debugging tools, and lets you install other tools in an ephemeral, writable layer that only exists during the debugging session.
By default image variants intended for runtime, run as a nonroot user. Ensure that necessary files and directories are accessible to that user. You may need to copy files to different directories or change permissions so your application running as a nonroot user can access them.
To view the user for an image variant, select the Tags tab for this repository.
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, even if you map it to a lower port on
the host. For example, docker run -p 80:8080 my-image will work because the port inside the container is 8080, and
docker run -p 80:81 my-image won't work because the port inside the container is 81.
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. In addition, use Docker Debug to debug containers
with no shell.
To see if a shell is available in an image variant and which one, select the Tags tab for this repository.
Ghost hardened images may have different entry points than images such as Docker Official Images.
To view the Entrypoint or CMD defined for an image variant, select the Tags tab for this repository, select a tag, and then select the Specifications tab.