guides: remove init

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

Author: craig-osterhout

content/get-started/docker-concepts/building-images/writing-a-dockerfile.md

@@ -147,21 +147,14 @@ Now that you have the project, you’re ready to create the `Dockerfile`.
 > build cache, run as a non-root user, and multi-stage builds.
 
 
-> **Containerize new projects quickly with `docker init`**
->
-> The `docker init` command will analyze your project and quickly create 
-> a Dockerfile, a `compose.yaml`, and a `.dockerignore`, helping you get
-> up and going. Since you're learning about Dockerfiles specifically here, 
-> you won't use it now. But, [learn more about it here](/reference/cli/docker/init/).
-
 ## Additional resources
 
 To learn more about writing a Dockerfile, visit the following resources:
 
 * [Dockerfile reference](/reference/dockerfile/)
 * [Dockerfile best practices](/develop/develop-images/dockerfile_best-practices/)
 * [Base images](/build/building/base-images/)
-* [Getting started with Docker Init](/reference/cli/docker/init/)
+* [Gordon](/ai/gordon/) — Docker's AI assistant can generate a Dockerfile for your project. Ask Gordon to analyze your code and suggest a Dockerfile optimized for your language and framework.
 
 ## Next steps
 

content/guides/angular/containerize.md

@@ -43,78 +43,15 @@ $ git clone https://github.com/kristiyan-velkov/docker-angular-sample
 ```
 ---
 
-## Generate a Dockerfile
-
-Docker provides an interactive CLI tool called `docker init` that helps scaffold the necessary configuration files for containerizing your application. This includes generating a `Dockerfile`, `.dockerignore`, `compose.yaml`, and `README.Docker.md`.
-
-To begin, navigate to the root of your project directory:
-
-```console
-$ cd docker-angular-sample
-```
-
-Then run the following command:
-
-```console
-$ docker init
-```
-You’ll see output similar to:
-
-```text
-Welcome to the Docker Init CLI!
-
-This utility will walk you through creating the following files with sensible defaults for your project:
-  - .dockerignore
-  - Dockerfile
-  - compose.yaml
-  - README.Docker.md
-
-Let's get started!
-```
-
-The CLI will prompt you with a few questions about your app setup.
-For consistency, please use the same responses shown in the example below when prompted:
-| Question                                                   | Answer          |
-|------------------------------------------------------------|-----------------|
-| What application platform does your project use?           | Node            |
-| What version of Node do you want to use?                   | 24.12.0-alpine  |
-| Which package manager do you want to use?                  | npm             |
-| Do you want to run "npm run build" before starting server? | yes             |
-| What directory is your build output to?                    | dist            |
-| What command do you want to use to start the app?          | npm run start   |
-| What port does your server listen on?                      | 8080            |
-
-After completion, your project directory will contain the following new files:
-
-```text
-├── docker-angular-sample/
-│ ├── Dockerfile
-│ ├── .dockerignore
-│ ├── compose.yaml
-│ └── README.Docker.md
-```
-
----
-
 ## Build the Docker image
 
-The default Dockerfile generated by `docker init` serves as a solid starting point for general Node.js applications. However, Angular is a front-end framework that compiles into static assets, so we need to tailor the Dockerfile to optimize for how Angular applications are built and served in a production environment.
-
-### Step 1: Improve the generated Dockerfile and configuration
+Angular is a front-end framework that compiles into static assets, so the Dockerfile uses a multi-stage build: one stage compiles the app with Node.js, and a second minimal stage serves the static output with Nginx.
 
-In this step, you’ll improve the Dockerfile and configuration files by following best practices:
-
-- Use multi-stage builds to keep the final image clean and small  
-- Serve the app using Nginx, a fast and secure web server  
-- Improve performance and security by only including what’s needed  
-
-These updates help ensure your app is easy to deploy, fast to load, and production-ready.
-
-> [!NOTE]
-> A `Dockerfile` is a plain text file that contains step-by-step instructions to build a Docker image. It automates packaging your application along with its dependencies and runtime environment.  
-> For full details, see the [Dockerfile reference](/reference/dockerfile/).
+> [!TIP]
+>
+> [Gordon](/ai/gordon/), Docker's AI assistant, can generate Docker assets for your project. Ask Gordon to create a Dockerfile, Compose file, and `.dockerignore` tailored to your application.
 
-### Step 2: Configure the Dockerfile
+### Step 1: Create the Dockerfile
 
 Before creating a Dockerfile, you need to choose a base image. You can either use the [Node.js Official Image](https://hub.docker.com/_/node) or a Docker Hardened Image (DHI) from the [Hardened Image catalog](https://hub.docker.com/hardened-images/catalog).
 
@@ -191,7 +128,7 @@ CMD ["-g", "daemon off;"]
 {{< /tab >}}
 {{< tab name="Using the Docker Official Image" >}}
 
-Now you need to create a production-ready multi-stage Dockerfile. Replace the generated Dockerfile with the following optimized configuration:
+Create a file named `Dockerfile` with the following contents:
 
 ```dockerfile
 # =========================================
@@ -252,7 +189,20 @@ CMD ["-g", "daemon off;"]
 {{< /tab >}}
 {{< /tabs >}}
 
-### Step 3: Configure the .dockerignore file
+### Step 2: Create the compose.yaml file
+
+Create a file named `compose.yaml` with the following contents:
+
+```yaml {collapse=true,title=compose.yaml}
+services:
+  server:
+    build:
+      context: .
+    ports:
+      - 8080:8080
+```
+
+### Step 3: Create the .dockerignore file
 
 The `.dockerignore` file tells Docker which files and folders to exclude when building the image.
 
@@ -264,7 +214,7 @@ The `.dockerignore` file tells Docker which files and folders to exclude when bu
 >
 > To learn more, visit the [.dockerignore reference](/reference/dockerfile.md#dockerignore-file).
 
-Copy and replace the contents of your existing `.dockerignore` with the configuration below:
+Create a file named `.dockerignore` with the following contents:
 
 ```dockerignore
 # ================================
@@ -434,8 +384,7 @@ After completing the previous steps, your project directory should now contain t
 │ ├── Dockerfile
 │ ├── .dockerignore
 │ ├── compose.yaml
-│ ├── nginx.conf
-│ └── README.Docker.md
+│ └── nginx.conf
 ```
 
 Now that your Dockerfile is configured, you can build the Docker image for your Angular application.
@@ -455,7 +404,7 @@ What this command does:
 - Tags the image as docker-angular-sample so you can reference it later
 
 
-#### Step 6:  View local images
+### Step 6: View local images
 
 After building your Docker image, you can check which images are available on your local machine using either the Docker CLI or [Docker Desktop](/manuals/desktop/use-desktop/images.md). Since you're already working in the terminal, let's use the Docker CLI.
 
@@ -547,9 +496,8 @@ $ docker compose down
 In this guide, you learned how to containerize, build, and run an Angular application using Docker. By following best practices, you created a secure, optimized, and production-ready setup.
 
 What you accomplished:
-- Initialized your project using `docker init` to scaffold essential Docker configuration files.
-- Replaced the default `Dockerfile` with a multi-stage build that compiles the Angular application and serves the static files using Nginx.
-- Replaced the default `.dockerignore` file to exclude unnecessary files and keep the image clean and efficient.
+- Created a multi-stage `Dockerfile` that compiles the Angular application and serves the static files using Nginx.
+- Created a `.dockerignore` file to exclude unnecessary files and keep the image clean and efficient.
 - Built your Docker image using `docker build`.
 - Ran the container using `docker compose up`, both in the foreground and in detached mode.
 - Verified that the app was running by visiting [http://localhost:8080](http://localhost:8080).
@@ -566,7 +514,6 @@ Explore official references and best practices to sharpen your Docker workflow:
 - [Multi-stage builds](/build/building/multi-stage/) – Learn how to separate build and runtime stages.
 - [Best practices for writing Dockerfiles](/develop/develop-images/dockerfile_best-practices/) – Write efficient, maintainable, and secure Dockerfiles.  
 - [Build context in Docker](/build/concepts/context/) – Learn how context affects image builds.  
-- [`docker init` CLI reference](/reference/cli/docker/init/) – Scaffold Docker assets automatically.
 - [`docker build` CLI reference](/reference/cli/docker/image/build/) – Build Docker images from a Dockerfile.
 - [`docker images` CLI reference](/reference/cli/docker/image/ls/) – Manage and inspect local Docker images.
 - [`docker compose up` CLI reference](/reference/cli/docker/compose/up/) – Start and run multi-container applications.

content/guides/angular/develop.md

@@ -112,8 +112,7 @@ After completing the previous steps, your project directory should now contain t
 │ ├── Dockerfile.dev
 │ ├── .dockerignore
 │ ├── compose.yaml
-│ ├── nginx.conf
-│ └── README.Docker.md
+│ └── nginx.conf
 ```
 
 ### Step 4: Start Compose Watch

content/guides/angular/run-tests.md

@@ -79,8 +79,7 @@ After completing the previous steps, your project directory should contain the f
 │ ├── Dockerfile.dev
 │ ├── .dockerignore
 │ ├── compose.yaml
-│ ├── nginx.conf
-│ └── README.Docker.md
+│ └── nginx.conf
 ```
 
 ### Step 2: Run the tests