From 3355f978a82bb6c88f1b4f96e0ba7cfe97df2c05 Mon Sep 17 00:00:00 2001 From: Craig Osterhout Date: Tue, 13 Jan 2026 10:39:05 -0800 Subject: [PATCH] dhi: wording update (#23971) ## Description Minor wording change. ## Related issues or tickets Issue raised in #23963 ## Reviews - [ ] Editorial review Signed-off-by: Craig Osterhout --- content/manuals/dhi/migration/migrate-from-doi.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/manuals/dhi/migration/migrate-from-doi.md b/content/manuals/dhi/migration/migrate-from-doi.md index ffecf66699..521733545f 100644 --- a/content/manuals/dhi/migration/migrate-from-doi.md +++ b/content/manuals/dhi/migration/migrate-from-doi.md @@ -30,7 +30,7 @@ When migrating from non-hardened images to DHI, be aware of these key difference | TLS certificates | May need to be installed | Contain standard TLS certificates by default. There is no need to install TLS certificates. | | Ports | Can bind to privileged ports (below 1024) when running as root | Run as a nonroot user by default. Applications can't bind to privileged ports (below 1024) when running in Kubernetes or in Docker Engine versions older than 20.10. Configure your application to listen on port 1025 or higher inside the container. | | Entry point | Varies by image | May have different entry points than Docker Official Images. Inspect entry points and update your Dockerfile if necessary. | -| No shell | Shell generally available in all images | Runtime images don't contain a shell. Use `dev` images in build stages to run shell commands and then copy artifacts to the runtime stage. | +| Shell | Shell generally available in all images | Runtime images don't contain a shell. Use `dev` images in build stages to run shell commands and then copy artifacts to the runtime stage. | ## Migration steps