dhi: add single stage migration examples

Signed-off-by: Craig <craig.osterhout@docker.com>

Author: craig-osterhout

content/manuals/dhi/how-to/migrate.md

@@ -63,6 +63,13 @@ replaced by the new hardened image.
 
 ### Step 2: Update the runtime image in your Dockerfile
 
+> [!NOTE]
+>
+> Using a multi-stage build is not strictly required, but it is highly
+> recommended to ensure that your final image is as minimal and secure as
+> possible. `dev` variant images have near-zero known CVEs, but they have
+> a larger attack surface than runtime images.
+
 To ensure that your final image is as minimal as possible, you should use a
 [multi-stage build](/manuals/build/building/multi-stage.md). All stages in your
 Dockerfile should use a hardened image. While intermediary stages will typically
@@ -78,7 +85,9 @@ examples of how to update your Dockerfile.
 ## Example Dockerfile migrations
 
 The following migration examples show a Dockerfile before the migration and
-after the migration.
+after the migration. The examples include both multi-stage and single-stage
+builds. While multi-stage builds are recommended, single-stage builds are also
+supported.
 
 ### Go example
 
@@ -98,7 +107,7 @@ ENTRYPOINT ["/app/main"]
 ```
 
 {{< /tab >}}
-{{< tab name="After" >}}
+{{< tab name="After (multi-stage)" >}}
 
 ```dockerfile
 #syntax=docker/dockerfile:1
@@ -118,6 +127,30 @@ COPY --from=builder /app/main  /app/main
 
 ENTRYPOINT ["/app/main"]
 ```
+
+{{< /tab >}}
+{{< tab name="After (single-stage)" >}}
+
+> [!NOTE]
+>
+> Using a multi-stage build is not strictly required, but it is highly
+> recommended to ensure that your final image is as minimal and secure as
+> possible. `dev` variant images have near-zero known CVEs, but they have
+> a larger attack surface than runtime images.
+
+
+```dockerfile
+#syntax=docker/dockerfile:1
+
+FROM <your-namespace>/dhi-golang:1-alpine3.21-dev
+
+WORKDIR /app
+ADD . ./
+RUN CGO_ENABLED=0 GOOS=linux go build -a -ldflags="-s -w" --installsuffix cgo -o main .
+
+ENTRYPOINT ["/app/main"]
+```
+
 {{< /tab >}}
 {{< /tabs >}}
 
@@ -142,7 +175,7 @@ CMD ["node", "index.js"]
 ```
 
 {{< /tab >}}
-{{< tab name="After" >}}
+{{< tab name="After (multi-stage)" >}}
 
 ```dockerfile
 #syntax=docker/dockerfile:1
@@ -167,6 +200,33 @@ WORKDIR /app
 
 CMD ["index.js"]
 ```
+
+{{< /tab >}}
+{{< tab name="After (single-stage)" >}}
+
+> [!NOTE]
+>
+> Using a multi-stage build is not strictly required, but it is highly
+> recommended to ensure that your final image is as minimal and secure as
+> possible. `dev` variant images have near-zero known CVEs, but they have
+> a larger attack surface than runtime images.
+
+
+```dockerfile
+#syntax=docker/dockerfile:1
+
+FROM <your-namespace>/dhi-node:23-alpine3.21-dev
+WORKDIR /usr/src/app
+
+COPY package*.json ./
+RUN npm install
+
+COPY image.jpg ./image.jpg
+COPY . .
+
+CMD ["index.js"]
+```
+
 {{< /tab >}}
 {{< /tabs >}}
 
@@ -206,7 +266,7 @@ ENTRYPOINT [ "python", "/app/image.py" ]
 ```
 
 {{< /tab >}}
-{{< tab name="After" >}}
+{{< tab name="After (multi-stage)" >}}
 
 ```dockerfile
 #syntax=docker/dockerfile:1
@@ -240,12 +300,43 @@ COPY --from=builder /app/venv /app/venv
 ENTRYPOINT [ "python", "/app/image.py" ]
 ```
 
+{{< /tab >}}
+{{< tab name="After (single-stage)" >}}
+
+> [!NOTE]
+>
+> Using a multi-stage build is not strictly required, but it is highly
+> recommended to ensure that your final image is as minimal and secure as
+> possible. `dev` variant images have near-zero known CVEs, but they have
+> a larger attack surface than runtime images.
+
+
+```dockerfile
+#syntax=docker/dockerfile:1
+
+FROM <your-namespace>/dhi-python:3.13-alpine3.21-dev
+
+ENV LANG=C.UTF-8
+ENV PYTHONDONTWRITEBYTECODE=1
+ENV PYTHONUNBUFFERED=1
+
+WORKDIR /app
+
+COPY requirements.txt .
+RUN pip install --no-cache-dir -r requirements.txt
+
+COPY image.py image.png ./
+
+ENTRYPOINT [ "python", "/app/image.py" ]
+```
+
 {{< /tab >}}
 {{< /tabs >}}
 
 ### Use Gordon
 
-Alternatively, you can request assistance to 
-[Gordon](/manuals/ai/gordon/_index.md), Docker's AI-powered assistant, to migrate your Dockerfile:
+Alternatively, you can request assistance to
+[Gordon](/manuals/ai/gordon/_index.md), Docker's AI-powered assistant, to
+migrate your Dockerfile:
 
 {{% include "gordondhi.md" %}}