updated DHI in .NET 10 guide

Author: brandonh6k

content/guides/dotnet/containerize.md

@@ -46,9 +46,22 @@ Now that you have an application, you can create the necessary Docker assets to
 {{< tabs >}}
 {{< tab name="Using Docker Hardened Images" >}}
 
-Docker Hardened Images (DHIs) for .NET are available on [Docker Hub](https://hub.docker.com/hardened-images/catalog/dhi/aspnetcore). Unlike using the Docker Official Image, you must first mirror the image into your organization. Follow the instructions in the [DHI quickstart](/dhi/get-started/) to create a mirrored repository.
+Docker Hardened Images (DHIs) for .NET are available in the [Docker Hardened Images catalog](https://hub.docker.com/hardened-images/catalog/dhi/aspnetcore). Docker Hardened Images are freely available to everyone with no subscription required. You can pull and use them like any other Docker image after signing in to the DHI registry. For more information, see the [DHI quickstart](/dhi/get-started/) guide.
 
-Mirrored repositories must start with `dhi-`, for example: `FROM <your-namespace>/dhi-aspnetcore:<tag>`.
+1. Sign in to the DHI registry:
+   ```console
+   $ docker login dhi.io
+   ```
+
+2. Pull the .NET SDK DHI (check the catalog for available versions):
+   ```console
+   $ docker pull dhi.io/dotnet:10-sdk
+   ```
+
+3. Pull the ASP.NET Core runtime DHI (check the catalog for available versions):
+   ```console
+   $ docker pull dhi.io/aspnetcore:10
+   ```
 
 You can use `docker init` to generate Docker assets, then modify the Dockerfile to use DHI images:
 
@@ -70,27 +83,27 @@ Let's get started!
 ? What local port do you want to use to access your server? 8080
 ```
 
-Then update your Dockerfile to use DHI images:
+In the following Dockerfile, the `FROM` instructions use `dhi.io/dotnet:10-sdk` and `dhi.io/aspnetcore:10` as the base images.
 
 ```dockerfile {title=Dockerfile}
 # syntax=docker/dockerfile:1
 
-FROM --platform=$BUILDPLATFORM <your-namespace>/dhi-dotnet:10-sdk AS build
+FROM --platform=$BUILDPLATFORM dhi.io/dotnet:10-sdk AS build
 ARG TARGETARCH
 COPY . /source
 WORKDIR /source/src
 RUN --mount=type=cache,id=nuget,target=/root/.nuget/packages \
     dotnet publish -a ${TARGETARCH/amd64/x64} --use-current-runtime --self-contained false -o /app
 
-FROM <your-namespace>/dhi-aspnetcore:10
+FROM dhi.io/aspnetcore:10
 WORKDIR /app
 COPY --from=build /app .
 ENTRYPOINT ["dotnet", "myWebApp.dll"]
 ```
 
 > [!NOTE]
 >
-> DHI runtime images already run as a non-root user (`nonroot`), so there's no need to create a user or specify `USER` in your Dockerfile. This reduces the attack surface and simplifies your configuration.
+> DHI runtime images already run as a non-root user (`nonroot`, UID 65532), so there's no need to create a user or specify `USER` in your Dockerfile. This reduces the attack surface and simplifies your configuration.
 
 {{< /tab >}}
 {{< tab name="Using the official .NET 10 image" >}}

content/guides/dotnet/develop.md

@@ -310,19 +310,19 @@ The following is the updated Dockerfile.
 ```Dockerfile {hl_lines="10-13"}
 # syntax=docker/dockerfile:1
 
-FROM --platform=$BUILDPLATFORM <your-namespace>/dhi-dotnet:10-sdk AS build
+FROM --platform=$BUILDPLATFORM dhi.io/dotnet:10-sdk AS build
 ARG TARGETARCH
 COPY . /source
 WORKDIR /source/src
 RUN --mount=type=cache,id=nuget,target=/root/.nuget/packages \
     dotnet publish -a ${TARGETARCH/amd64/x64} --use-current-runtime --self-contained false -o /app
 
-FROM <your-namespace>/dhi-dotnet:10-sdk AS development
+FROM dhi.io/dotnet:10-sdk AS development
 COPY . /source
 WORKDIR /source/src
 CMD dotnet run --no-launch-profile
 
-FROM <your-namespace>/dhi-aspnetcore:10
+FROM dhi.io/aspnetcore:10
 WORKDIR /app
 COPY --from=build /app .
 ENTRYPOINT ["dotnet", "myWebApp.dll"]
@@ -409,7 +409,7 @@ secrets:
     file: db/password.txt
 ```
 
-Your containerized application will now use the SDK image (either `<your-namespace>/dhi-dotnet:10-sdk` for DHI or `mcr.microsoft.com/dotnet/sdk:10.0-alpine` for official images), which includes development tools like `dotnet test`. Continue to the next section to learn how you can run `dotnet test`.
+Your containerized application will now use the SDK image (either `dhi.io/dotnet:10-sdk` for DHI or `mcr.microsoft.com/dotnet/sdk:10.0-alpine` for official images), which includes development tools like `dotnet test`. Continue to the next section to learn how you can run `dotnet test`.
 
 ## Summary
 

content/guides/dotnet/run-tests.md

@@ -53,20 +53,20 @@ The following is the updated Dockerfile.
 ```dockerfile {hl_lines="9"}
 # syntax=docker/dockerfile:1
 
-FROM --platform=$BUILDPLATFORM <your-namespace>/dhi-dotnet:10-sdk AS build
+FROM --platform=$BUILDPLATFORM dhi.io/dotnet:10-sdk AS build
 ARG TARGETARCH
 COPY . /source
 WORKDIR /source/src
 RUN --mount=type=cache,id=nuget,target=/root/.nuget/packages \
     dotnet publish -a ${TARGETARCH/amd64/x64} --use-current-runtime --self-contained false -o /app
 RUN dotnet test /source/tests
 
-FROM <your-namespace>/dhi-dotnet:10-sdk AS development
+FROM dhi.io/dotnet:10-sdk AS development
 COPY . /source
 WORKDIR /source/src
 CMD dotnet run --no-launch-profile
 
-FROM <your-namespace>/dhi-aspnetcore:10
+FROM dhi.io/aspnetcore:10
 WORKDIR /app
 COPY --from=build /app .
 ENTRYPOINT ["dotnet", "myWebApp.dll"]

content/guides/nodejs/containerize.md

@@ -323,17 +323,25 @@ Choosing DHI offers the advantage of a production-ready image that is lightweigh
 
 {{< tabs >}}
 {{< tab name="Using Docker Hardened Images" >}}
-Docker Hardened Images (DHIs) are available for Node.js on [Docker Hub](https://hub.docker.com/hardened-images/catalog/dhi/node). Unlike using the Docker Official Image, you must first mirror the Node.js image into your organization and then use it as your base image. Follow the instructions in the [DHI quickstart](/dhi/get-started/) to create a mirrored repository for Node.js.
+Docker Hardened Images (DHIs) are available for Node.js in the [Docker Hardened Images catalog](https://hub.docker.com/hardened-images/catalog/dhi/node). Docker Hardened Images are freely available to everyone with no subscription required. You can pull and use them like any other Docker image after signing in to the DHI registry. For more information, see the [DHI quickstart](/dhi/get-started/) guide.
 
-Mirrored repositories must start with `dhi-`, for example: `FROM <your-namespace>/dhi-node:<tag>`. In the following Dockerfile, the `FROM` instruction uses `<your-namespace>/dhi-node:24-alpine3.22-dev` as the base image.
+1. Sign in to the DHI registry:
+
+   $ docker login dhi.io
+
+2. Pull the Node.js DHI (check the catalog for available versions):
+
+   $ docker pull dhi.io/node:24-alpine3.22-dev
+
+In the following Dockerfile, the `FROM` instruction uses `dhi.io/node:24-alpine3.22-dev` as the base image.
 
 ```dockerfile
 # ========================================
 # Optimized Multi-Stage Dockerfile
 # Node.js TypeScript Application (Using DHI)
 # ========================================
 
-FROM <your-namespace>/dhi-node:24-alpine3.22-dev AS base
+FROM dhi.io/node:24-alpine3.22-dev AS base
 
 # Set working directory
 WORKDIR /app
@@ -419,7 +427,7 @@ CMD ["npm", "run", "dev:docker"]
 # ========================================
 # Production Stage
 # ========================================
-FROM <your-namespace>/dhi-node:24-alpine3.22-dev AS production
+FROM dhi.io/node:24-alpine3.22-dev AS production
 
 # Set working directory
 WORKDIR /app

content/guides/python/containerize.md

@@ -14,7 +14,7 @@ aliases:
 ## Prerequisites
 
 - You have installed the latest version of [Docker Desktop](/get-started/get-docker.md).
-- You have a [git client](https://git-scm.com/downloads). The examples in this section use a command-line based git client, but you can use any client.
+- You have a [Git client](https://git-scm.com/downloads). The examples in this section use a command-line based Git client, but you can use any client.
 
 ## Overview
 
@@ -314,8 +314,19 @@ venv.bak/
 {{< /tab >}}
 {{< tab name="Using Docker Hardened Image" >}}
 
-If you don't have Docker Desktop installed or prefer creating the assets
-manually, you can create the following files in your project directory.
+Docker Hardened Images (DHIs) are available for Python in the [Docker Hardened Images catalog](https://hub.docker.com/hardened-images/catalog/dhi/python). Docker Hardened Images are freely available to everyone with no subscription required. You can pull and use them like any other Docker image after signing in to the DHI registry. For more information, see the [DHI quickstart](/dhi/get-started/) guide.
+
+1. Sign in to the DHI registry:
+
+   ```console
+   $ docker login dhi.io
+   ```
+
+2. Pull the Python DHI (check the catalog for available versions):
+
+   ```console
+   $ docker pull dhi.io/python:3.12.12-debian13-fips-dev
+   ```
 
 Create a file named `Dockerfile` with the following contents.
 
@@ -331,7 +342,7 @@ Create a file named `Dockerfile` with the following contents.
 # This Dockerfile uses Docker Hardened Images (DHI) for enhanced security.
 # For more information, see https://docs.docker.com/dhi/
 ARG PYTHON_VERSION=3.12.12-debian13-fips-dev
-FROM <your-workspace>/dhi-python:${PYTHON_VERSION}
+FROM dhi.io/python:${PYTHON_VERSION}
 
 # Prevents Python from writing pyc files.
 ENV PYTHONDONTWRITEBYTECODE=1