From b1256d572f75131b9feb85c30fb1c25f9813dcb5 Mon Sep 17 00:00:00 2001 From: Allie Sadler <102604716+aevesdocker@users.noreply.github.com> Date: Tue, 22 Oct 2024 11:25:13 +0100 Subject: [PATCH] ENGDOCS-2265 (#21203) * ENGDOCS-2265 * Apply suggestions from code review --- content/contribute/components/call-outs.md | 4 +-- .../multi-container-applications.md | 16 ++++----- .../overriding-container-defaults.md | 10 +++--- .../persisting-container-data.md | 6 ++-- .../running-containers/publishing-ports.md | 4 +-- .../running-containers/sharing-local-files.md | 22 +++++------- .../the-basics/what-is-a-container.md | 14 ++++---- .../the-basics/what-is-an-image.md | 12 +++---- .../get-started/workshop/08_using_compose.md | 8 ++--- content/guides/databases.md | 20 +++++------ content/guides/localstack.md | 6 ++-- .../desktop/dev-environments/_index.md | 4 +-- content/manuals/desktop/faqs/linuxfaqs.md | 4 +-- content/manuals/desktop/faqs/macfaqs.md | 2 +- content/manuals/desktop/faqs/releases.md | 2 +- content/manuals/desktop/feedback.md | 2 +- content/manuals/desktop/kubernetes.md | 6 ++-- content/manuals/desktop/release-notes.md | 34 +++++++++---------- content/manuals/desktop/settings.md | 10 +++--- .../desktop/synchronized-file-sharing.md | 2 +- content/manuals/desktop/uninstall.md | 2 +- content/manuals/desktop/use-desktop/_index.md | 16 ++++----- content/manuals/desktop/use-desktop/builds.md | 2 +- .../manuals/desktop/use-desktop/container.md | 2 +- content/manuals/desktop/use-desktop/pause.md | 6 ++-- .../manuals/desktop/use-desktop/volumes.md | 4 +-- .../extensions-sdk/architecture/_index.md | 2 +- .../build/backend-extension-tutorial.md | 4 +-- .../build/minimal-frontend-extension.md | 2 +- .../dev/continuous-integration.md | 4 +-- content/manuals/extensions/marketplace.md | 6 ++-- content/manuals/extensions/non-marketplace.md | 6 ++-- .../manuals/extensions/settings-feedback.md | 4 +-- content/manuals/harmonia/_index.md | 16 ++++----- 34 files changed, 130 insertions(+), 134 deletions(-) diff --git a/content/contribute/components/call-outs.md b/content/contribute/components/call-outs.md index 261cef77d2f..24455b7837f 100644 --- a/content/contribute/components/call-outs.md +++ b/content/contribute/components/call-outs.md @@ -46,7 +46,7 @@ is displayed in the callout. > `docker compose down`. If you want to remove the volumes, you will need to add > the `--volumes` flag. > -> The Docker Dashboard does not remove volumes when you delete the app stack. +> The Docker Desktop Dashboard does not remove volumes when you delete the app stack. > [!CAUTION] > @@ -96,7 +96,7 @@ Docker Scout is an [early access](/release-lifecycle/#early-access-ea) product. > `docker compose down`. If you want to remove the volumes, you will need to add > the `--volumes` flag. > -> The Docker Dashboard does _not_ remove volumes when you delete the app stack. +> The Docker Desktop Dashboard does not remove volumes when you delete the app stack. > [!CAUTION] > diff --git a/content/get-started/docker-concepts/running-containers/multi-container-applications.md b/content/get-started/docker-concepts/running-containers/multi-container-applications.md index a674f4077fe..061a7333ed1 100644 --- a/content/get-started/docker-concepts/running-containers/multi-container-applications.md +++ b/content/get-started/docker-concepts/running-containers/multi-container-applications.md @@ -157,9 +157,9 @@ In this hands-on guide, you'll first see how to build and run a counter web appl 008e0ecf4f36 redis "docker-entrypoint.s…" About a minute ago Up About a minute 6379/tcp redis ``` -7. If you look at the Docker Dashboard, you can see the containers and dive deeper into their configuration. +7. If you look at the Docker Desktop Dashboard, you can see the containers and dive deeper into their configuration. - ![A screenshot of Docker Dashboard showing multi-container applications](images/multi-container-apps.webp?w=5000&border=true) + ![A screenshot of the Docker Desktop Dashboard showing multi-container applications](images/multi-container-apps.webp?w=5000&border=true) 8. With everything up and running, you can open [http://localhost](http://localhost) in your browser to see the site. Refresh the page several times to see the host that’s handling the request and the total number of requests: @@ -174,9 +174,9 @@ In this hands-on guide, you'll first see how to build and run a counter web appl > > You might have noticed that Nginx, acting as a reverse proxy, likely distributes incoming requests in a round-robin fashion between the two backend containers. This means each request might be directed to a different container (web1 and web2) on a rotating basis. The output shows consecutive increments for both the web1 and web2 containers and the actual counter value stored in Redis is updated only after the response is sent back to the client. -9. You can use the Docker Dashboard to remove the containers by selecting the containers and selecting the **Delete** button. +9. You can use the Docker Desktop Dashboard to remove the containers by selecting the containers and selecting the **Delete** button. - ![A screenshot of Docker Dashboard showing how to delete the multi-container applications](images/delete-multi-container-apps.webp?border=true) + ![A screenshot of Docker Desktop Dashboard showing how to delete the multi-container applications](images/delete-multi-container-apps.webp?border=true) ## Simplify the deployment using Docker Compose @@ -204,14 +204,14 @@ Navigate to the root of the project directory. Inside this directory, you'll fin ✔ Container nginx-nodejs-redis-nginx-1 Started ``` -2. If you look at the Docker Dashboard, you can see the containers and dive deeper into their configuration. +2. If you look at the Docker Desktop Dashboard, you can see the containers and dive deeper into their configuration. - ![A screenshot of Docker Dashboard showing the containers of the application stack deployed using Docker Compose](images/list-containers.webp?border=true) + ![A screenshot of the Docker Desktop Dashboard showing the containers of the application stack deployed using Docker Compose](images/list-containers.webp?border=true) -3. Alternatively, you can use the Docker Dashboard to remove the containers by selecting the application stack and selecting the **Delete** button. +3. Alternatively, you can use the Docker Desktop Dashboard to remove the containers by selecting the application stack and selecting the **Delete** button. - ![A screenshot of Docker Dashboard that shows how to remove the containers that you deployed using Docker Compose](images/delete-containers.webp?border=true) + ![A screenshot of Docker Desktop Dashboard that shows how to remove the containers that you deployed using Docker Compose](images/delete-containers.webp?border=true) In this guide, you learned how easy it is to use Docker Compose to start and stop a multi-container application compared to `docker run` which is error-prone and difficult to manage. diff --git a/content/get-started/docker-concepts/running-containers/overriding-container-defaults.md b/content/get-started/docker-concepts/running-containers/overriding-container-defaults.md index 87b14a80a4f..5f06a26b8ef 100644 --- a/content/get-started/docker-concepts/running-containers/overriding-container-defaults.md +++ b/content/get-started/docker-concepts/running-containers/overriding-container-defaults.md @@ -89,9 +89,9 @@ In this hands-on guide, you'll see how to use the `docker run` command to overri This will start another Postgres container in the background, listening on the standard postgres port `5432` in the container, but mapped to port `5433` on the host machine. You override the host port just to ensure that this new container doesn't conflict with the existing running container. -3. Verify that both containers are running by going to the **Containers** view in the Docker Dashboard. +3. Verify that both containers are running by going to the **Containers** view in the Docker Desktop Dashboard. - ![A screenshot of Docker Dashboard showing the running instances of Postgres containers](images/running-postgres-containers.webp?border=true) + ![A screenshot of the Docker Desktop Dashboard showing the running instances of Postgres containers](images/running-postgres-containers.webp?border=true) ### Run Postgres container in a controlled network @@ -170,15 +170,15 @@ Sometimes, you might need to override the default commands (`CMD`) or entry poin This command starts the Postgres service defined in the Docker Compose file. -3. Verify the authentication with Docker Dashboard. +3. Verify the authentication with Docker Desktop Dashboard. - Open the Docker Dashboard, select the **Postgres** container and select **Exec** to enter into the container shell. You can type the following command to connect to the Postgres database: + Open the Docker Desktop Dashboard, select the **Postgres** container and select **Exec** to enter into the container shell. You can type the following command to connect to the Postgres database: ```console # psql -U postgres ``` - ![A screenshot of the Docker Dashboard selecting the Postgres container and entering into its shell using EXEC button](images/exec-into-postgres-container.webp?border=true) + ![A screenshot of the Docker Desktop Dashboard selecting the Postgres container and entering into its shell using EXEC button](images/exec-into-postgres-container.webp?border=true) > [!NOTE] diff --git a/content/get-started/docker-concepts/running-containers/persisting-container-data.md b/content/get-started/docker-concepts/running-containers/persisting-container-data.md index a9ca760d142..bf75cb33e2c 100644 --- a/content/get-started/docker-concepts/running-containers/persisting-container-data.md +++ b/content/get-started/docker-concepts/running-containers/persisting-container-data.md @@ -128,9 +128,9 @@ In this guide, you’ll practice creating and using volumes to persist data crea ### View volume contents -The Docker Dashboard provides the ability to view the contents of any volume, as well as the ability to export, import, and clone volumes. +The Docker Desktop Dashboard provides the ability to view the contents of any volume, as well as the ability to export, import, and clone volumes. -1. Open the Docker Dashboard and navigate to the **Volumes** view. In this view, you should see the **postgres_data** volume. +1. Open the Docker Desktop Dashboard and navigate to the **Volumes** view. In this view, you should see the **postgres_data** volume. 2. Select the **postgres_data** volume’s name. @@ -149,7 +149,7 @@ $ docker rm -f new-db There are a few methods to remove volumes, including the following: -- Select the **Delete Volume** option on a volume in the Docker Dashboard. +- Select the **Delete Volume** option on a volume in the Docker Desktop Dashboard. - Use the `docker volume rm` command: ```console diff --git a/content/get-started/docker-concepts/running-containers/publishing-ports.md b/content/get-started/docker-concepts/running-containers/publishing-ports.md index 9f729444416..d2766459fbf 100644 --- a/content/get-started/docker-concepts/running-containers/publishing-ports.md +++ b/content/get-started/docker-concepts/running-containers/publishing-ports.md @@ -88,9 +88,9 @@ In this step, you will run a container and publish its port using the Docker CLI The first `8080` refers to the host port. This is the port on your local machine that will be used to access the application running inside the container. The second `80` refers to the container port. This is the port that the application inside the container listens on for incoming connections. Hence, the command binds to port `8080` of the host to port `80` on the container system. -3. Verify the published port by going to the **Containers** view of the Docker Dashboard. +3. Verify the published port by going to the **Containers** view of the Docker Desktop Dashboard. - ![A screenshot of Docker dashboard showing the published port](images/published-ports.webp?w=5000&border=true) + ![A screenshot of Docker Desktop Dashboard showing the published port](images/published-ports.webp?w=5000&border=true) 4. Open the website by either selecting the link in the **Port(s)** column of your container or visiting [http://localhost:8080](http://localhost:8080) in your browser. diff --git a/content/get-started/docker-concepts/running-containers/sharing-local-files.md b/content/get-started/docker-concepts/running-containers/sharing-local-files.md index 493bbd6cd82..93ead5d5bd7 100644 --- a/content/get-started/docker-concepts/running-containers/sharing-local-files.md +++ b/content/get-started/docker-concepts/running-containers/sharing-local-files.md @@ -90,9 +90,9 @@ In this hands-on guide, you’ll practice how to create and use a bind mount to Using a bind mount, you can map the configuration file on your host computer to a specific location within the container. In this example, you’ll see how to change the look and feel of the webpage by using bind mount: -1. Delete the existing container by using the Docker Dashboard: +1. Delete the existing container by using the Docker Desktop Dashboard: - ![A screenshot of Docker dashboard showing how to delete the httpd container](images/delete-httpd-container.webp?border=true) + ![A screenshot of Docker Desktop Dashboard showing how to delete the httpd container](images/delete-httpd-container.webp?border=true) 2. Create a new directory called `public_html` on your host system. @@ -157,20 +157,20 @@ Using a bind mount, you can map the configuration file on your host computer to With everything now up and running, you should be able to access the site via [http://localhost:8080](http://localhost:8080) and find a new webpage that welcomes you with a friendly whale. -### Access the file on the Docker Dashboard +### Access the file on the Docker Desktop Dashboard 1. You can view the mounted files inside a container by selecting the container's **Files** tab and then selecting a file inside the `/usr/local/apache2/htdocs/` directory. Then, select **Open file editor**. - ![A screenshot of Docker dashboard showing the mounted files inside the a container](images/mounted-files.webp?border=true) + ![A screenshot of Docker Desktop Dashboard showing the mounted files inside the a container](images/mounted-files.webp?border=true) -2. Delete the file on the host and verify the file is also deleted in the container. You will find that the files no longer exist under **Files** in the Docker Dashboard. +2. Delete the file on the host and verify the file is also deleted in the container. You will find that the files no longer exist under **Files** in the Docker Desktop Dashboard. - ![A screenshot of Docker dashboard showing the deleted files inside the a container](images/deleted-files.webp?border=true) + ![A screenshot of Docker Desktop Dashboard showing the deleted files inside the a container](images/deleted-files.webp?border=true) -3. Recreate the HTML file on the host system and see that file re-appears under the **Files** tab under **Containers** on the Docker Dashboard. By now, you will be able to access the site too. +3. Recreate the HTML file on the host system and see that file re-appears under the **Files** tab under **Containers** on the Docker Desktop Dashboard. By now, you will be able to access the site too. @@ -178,23 +178,19 @@ Using a bind mount, you can map the configuration file on your host computer to The container continues to run until you stop it. -1. Go to the **Containers** view in the Docker Dashboard. +1. Go to the **Containers** view in the Docker Desktop Dashboard. 2. Locate the container you'd like to stop. 3. Select the **Delete** action in the Actions column. - - - -![A screenshot of Docker dashboard showing how to delete the container](images/delete-the-container.webp?border=true) +![A screenshot of Docker Desktop Dashboard showing how to delete the container](images/delete-the-container.webp?border=true) ## Additional resources The following resources will help you learn more about bind mounts: - * [Manage data in Docker](/storage/) * [Volumes](/storage/volumes/) * [Bind mounts](/storage/bind-mounts/) diff --git a/content/get-started/docker-concepts/the-basics/what-is-a-container.md b/content/get-started/docker-concepts/the-basics/what-is-a-container.md index c8abe3f8036..89af955717e 100644 --- a/content/get-started/docker-concepts/the-basics/what-is-a-container.md +++ b/content/get-started/docker-concepts/the-basics/what-is-a-container.md @@ -56,7 +56,7 @@ Use the following instructions to run a container. 2. Specify `welcome-to-docker` in the search input and then select the **Pull** button. - ![A screenshot of the Docker Dashboard showing the search result for welcome-to-docker Docker image ](images/search-the-docker-image.webp?border=true&w=1000&h=700) + ![A screenshot of the Docker Desktop Dashboard showing the search result for welcome-to-docker Docker image ](images/search-the-docker-image.webp?border=true&w=1000&h=700) 3. Once the image is successfully pulled, select the **Run** button. @@ -66,7 +66,7 @@ Use the following instructions to run a container. 6. In the **Host port**, specify `8080`. - ![A screenshot of Docker Dashboard showing the container run dialog with welcome-to-docker typed in as the container name and 8080 specified as the port number](images/run-a-new-container.webp?border=true&w=550&h=400) + ![A screenshot of Docker Desktop Dashboard showing the container run dialog with welcome-to-docker typed in as the container name and 8080 specified as the port number](images/run-a-new-container.webp?border=true&w=550&h=400) 7. Select **Run** to start your container. @@ -74,7 +74,7 @@ Congratulations! You just ran your first container! 🎉 ### View your container -You can view all of your containers by going to the **Containers** view of the Docker Dashboard. +You can view all of your containers by going to the **Containers** view of the Docker Desktop Dashboard. ![Screenshot of the container view of the Docker Desktop GUI showing the welcome-to-docker container running on the host port 8080](images/view-your-containers.webp?border=true&w=750&h=600) @@ -92,25 +92,25 @@ For this container, the frontend is accessible on port `8080`. To open the websi Docker Desktop lets you explore and interact with different aspects of your container. Try it out yourself. -1. Go to the **Containers** view in the Docker Dashboard. +1. Go to the **Containers** view in the Docker Desktop Dashboard. 2. Select your container. 3. Select the **Files** tab to explore your container's isolated file system. - ![Screenshot of the Docker Dashboard showing the files and directories inside a running container](images/explore-your-container.webp?border) + ![Screenshot of the Docker Desktop Dashboard showing the files and directories inside a running container](images/explore-your-container.webp?border) ### Stop your container The `docker/welcome-to-docker` container continues to run until you stop it. -1. Go to the **Containers** view in the Docker Dashboard. +1. Go to the **Containers** view in the Docker Desktop Dashboard. 2. Locate the container you'd like to stop. 3. Select the **Stop** action in the **Actions** column. - ![Screenshot of the Docker Dashboard with the welcome container selected and being prepared to stop](images/stop-your-container.webp?border) + ![Screenshot of the Docker Desktop Dashboard with the welcome container selected and being prepared to stop](images/stop-your-container.webp?border) {{< /tab >}} {{< tab name="Using the CLI" >}} diff --git a/content/get-started/docker-concepts/the-basics/what-is-an-image.md b/content/get-started/docker-concepts/the-basics/what-is-an-image.md index 34f2a058112..fb31b9efb79 100644 --- a/content/get-started/docker-concepts/the-basics/what-is-an-image.md +++ b/content/get-started/docker-concepts/the-basics/what-is-an-image.md @@ -48,17 +48,17 @@ In this hands-on, you will learn how to search and pull a container image using ### Search for and download an image -1. Open the Docker Dashboard and select the **Images** view in the left-hand navigation menu. +1. Open the Docker Desktop Dashboard and select the **Images** view in the left-hand navigation menu. - ![A screenshot of the Docker Dashboard showing the image view on the left sidebar](images/click-image.webp?border=true&w=1050&h=400) + ![A screenshot of the Docker Desktop Dashboard showing the image view on the left sidebar](images/click-image.webp?border=true&w=1050&h=400) 2. Select the **Search images to run** button. If you don't see it, select the _global search bar_ at the top of the screen. - ![A screenshot of the Docker Dashboard showing the search ta](images/search-image.webp?border) + ![A screenshot of the Docker Desktop Dashboard showing the search ta](images/search-image.webp?border) 3. In the **Search** field, enter "welcome-to-docker". Once the search has completed, select the `docker/welcome-to-docker` image. - ![A screenshot of the Docker Dashboard showing the search results for the docker/welcome-to-docker image](images/select-image.webp?border=true&w=1050&h=400) + ![A screenshot of the Docker Desktop Dashboard showing the search results for the docker/welcome-to-docker image](images/select-image.webp?border=true&w=1050&h=400) 4. Select **Pull** to download the image. @@ -67,11 +67,11 @@ In this hands-on, you will learn how to search and pull a container image using Once you have an image downloaded, you can learn quite a few details about the image either through the GUI or the CLI. -1. In the Docker Dashboard, select the **Images** view. +1. In the Docker Desktop Dashboard, select the **Images** view. 2. Select the **docker/welcome-to-docker** image to open details about the image. - ![A screenshot of the Docker Dashboard showing the images view with an arrow pointing to the docker/welcome-to-docker image](images/pulled-image.webp?border=true&w=1050&h=400) + ![A screenshot of the Docker Desktop Dashboard showing the images view with an arrow pointing to the docker/welcome-to-docker image](images/pulled-image.webp?border=true&w=1050&h=400) 3. The image details page presents you with information regarding the layers of the image, the packages and libraries installed in the image, and any discovered vulnerabilities. diff --git a/content/get-started/workshop/08_using_compose.md b/content/get-started/workshop/08_using_compose.md index 2fb2d57d4a6..94f6e5e5a6c 100644 --- a/content/get-started/workshop/08_using_compose.md +++ b/content/get-started/workshop/08_using_compose.md @@ -253,9 +253,9 @@ Now that you have your `compose.yaml` file, you can start your application. 4. At this point, you should be able to open your app in your browser on [http://localhost:3000](http://localhost:3000) and see it running. -## See the app stack in Docker Dashboard +## See the app stack in Docker Desktop Dashboard -If you look at the Docker Dashboard, you'll see that there is a group named **getting-started-app**. This is the project name from Docker +If you look at the Docker Desktop Dashboard, you'll see that there is a group named **getting-started-app**. This is the project name from Docker Compose and used to group the containers together. By default, the project name is simply the name of the directory that the `compose.yaml` was located in. @@ -265,7 +265,7 @@ quickly see what container is your app and which container is the mysql database ## Tear it all down -When you're ready to tear it all down, simply run `docker compose down` or hit the trash can on the Docker Dashboard +When you're ready to tear it all down, simply run `docker compose down` or hit the trash can on the Docker Desktop Dashboard for the entire app. The containers will stop and the network will be removed. >**Warning** @@ -273,7 +273,7 @@ for the entire app. The containers will stop and the network will be removed. >By default, named volumes in your compose file are not removed when you run `docker compose down`. If you want to >remove the volumes, you need to add the `--volumes` flag. > ->The Docker Dashboard does not remove volumes when you delete the app stack. +>The Docker Desktop Dashboard does not remove volumes when you delete the app stack. ## Summary diff --git a/content/guides/databases.md b/content/guides/databases.md index 28b787cd2e2..a5f13f525a3 100644 --- a/content/guides/databases.md +++ b/content/guides/databases.md @@ -76,7 +76,7 @@ To verify that you container is running, run `docker ps` in a terminal To run a container using the GUI: -1. In the Docker Dashboard, select the global search at the top of the window. +1. In the Docker Desktop Dashboard, select the global search at the top of the window. 2. Specify `mysql` in the search box, and select the `Images` tab if not already selected. 3. Hover over the `msyql` image and select `Run`. @@ -92,7 +92,7 @@ To run a container using the GUI: ![The optional settings screen with the options specified.](images/databases-1.webp) 6. Select `Run`. -7. Open the **Container** view in the Docker Dashboard to verify that your +7. Open the **Container** view in the Docker Desktop Dashboard to verify that your container is running. {{< /tab >}} @@ -138,7 +138,7 @@ can run `exit` to return to your terminal. {{< /tab >}} {{< tab name="GUI" >}} -1. Open the Docker Dashboard and select the **Containers** view. +1. Open the Docker Desktop Dashboard and select the **Containers** view. 2. In the **Actions** column for your container, select **Show container actions** and then select **Open in terminal**. @@ -184,7 +184,7 @@ guide. To stop and remove a container, either: - In a terminal, run `docker remove --force my-mysql` to remove the container named `my-mysql`. -- Or, in the Docker Dashboard, select the **Delete** icon next to your +- Or, in the Docker Desktop Dashboard, select the **Delete** icon next to your container in the **Containers** view. Next, you can use either the Docker Desktop GUI or CLI to run the container with @@ -219,7 +219,7 @@ CONTAINER ID IMAGE COMMAND CREATED STATUS To run a container using the GUI: -1. In the Docker Dashboard, select the global search at the top of the window. +1. In the Docker Desktop Dashboard, select the global search at the top of the window. 2. Specify `mysql` in the search box, and select the `Images` tab if not already selected. 3. Hover over the `msyql` image and select `Run`. @@ -259,7 +259,7 @@ guide. To stop and remove a container, either: - In a terminal, run `docker remove --force my-mysql` to remove the container named `my-mysql`. -- Or, in the Docker Dashboard, select the **Delete** icon next to your +- Or, in the Docker Desktop Dashboard, select the **Delete** icon next to your container in the **Containers** view. To create a network and run containers on it: @@ -314,7 +314,7 @@ guide. To stop and remove a container, either: - In a terminal, run `docker remove --force my-mysql` to remove the container named `my-mysql`. -- Or, in the Docker Dashboard, select the **Delete** icon next to your +- Or, in the Docker Desktop Dashboard, select the **Delete** icon next to your container in the **Containers** view. Next, you can use either the Docker Desktop GUI or CLI to run the container with a volume. @@ -389,7 +389,7 @@ data persists: 1. Run a container with a volume attached. - 1. In the Docker Dashboard, select the global search at the top of the window. + 1. In the Docker Desktop Dashboard, select the global search at the top of the window. 2. Specify `mysql` in the search box, and select the **Images** tab if not already selected. 3. Hover over the **mysql** image and select **Run**. @@ -430,7 +430,7 @@ data persists: you created would be lost when deleting the container. 4. Run a container with a volume attached. - 1. In the Docker Dashboard, select the global search at the top of the window. + 1. In the Docker Desktop Dashboard, select the global search at the top of the window. 2. Specify `mysql` in the search box, and select the **Images** tab if not already selected. 3. Hover over the **mysql** image and select **Run**. @@ -489,7 +489,7 @@ guide. To stop and remove a container, either: - In a terminal, run `docker remove --force my-mysql` to remove the container named `my-mysql`. -- Or, in the Docker Dashboard, select the **Delete** icon next to your +- Or, in the Docker Desktop Dashboard, select the **Delete** icon next to your container in the **Containers** view. To build and run your custom image: diff --git a/content/guides/localstack.md b/content/guides/localstack.md index 09bbf4f1a9c..4d0ef10d774 100644 --- a/content/guides/localstack.md +++ b/content/guides/localstack.md @@ -65,7 +65,7 @@ Launch a quick demo of LocalStack by using the following steps: $ docker compose -f compose-native.yml up -d ``` - This Compose file also includes specifications for a required Mongo database. You can verify the services are up and running by visiting the Docker Dashboard. + This Compose file also includes specifications for a required Mongo database. You can verify the services are up and running by visiting the Docker Desktop Dashboard. ![Diagram showing the LocalStack and Mongo container up and running on Docker Desktop ](./images/launch-localstack.webp) @@ -91,7 +91,7 @@ Launch a quick demo of LocalStack by using the following steps: The command `s3 mb s3://mysamplebucket` tells the AWS CLI to create a new S3 bucket (mb stands for `make bucket`) named `mysamplebucket`. - You can verify if the S3 bucket gets created or not by selecting the LocalStack container on the Docker Dashboard and viewing the logs. The logs indicates that your LocalStack environment is configured correctly and you can now use the `mysamplebucket` for storing and retrieving objects. + You can verify if the S3 bucket gets created or not by selecting the LocalStack container on the Docker Desktop Dashboard and viewing the logs. The logs indicates that your LocalStack environment is configured correctly and you can now use the `mysamplebucket` for storing and retrieving objects. ![Diagram showing the logs of LocalStack that highlights the S3 bucket being created successfully ](./images/localstack-s3put.webp) @@ -287,7 +287,7 @@ Now that you have learnt how to connect a non-containerized Node.js application 3. Stop the running services - Ensure that you stop the Node frontend and backend service from the previous step by pressing “Ctrl+C” in the terminal. Also, you'll need to stop the LocalStack and Mongo containers by selecting them in the Docker Dashboard and selecting the "Delete" button. + Ensure that you stop the Node frontend and backend service from the previous step by pressing “Ctrl+C” in the terminal. Also, you'll need to stop the LocalStack and Mongo containers by selecting them in the Docker Desktop Dashboard and selecting the "Delete" button. 4. Start the application stack by executing the following command at the root of your cloned project directory: diff --git a/content/manuals/desktop/dev-environments/_index.md b/content/manuals/desktop/dev-environments/_index.md index 6fcb7843259..c13a82948ee 100644 --- a/content/manuals/desktop/dev-environments/_index.md +++ b/content/manuals/desktop/dev-environments/_index.md @@ -16,7 +16,7 @@ Dev Environments let you create a configurable developer environment with all th It uses tools built into code editors that allows Docker to access code mounted into a container rather than on your local host. This isolates the tools, files and running services on your machine allowing multiple versions of them to exist side by side. -You can use Dev Environments through the intuitive GUI in Docker Dashboard or straight from your terminal with the new [`docker dev` CLI plugin](dev-cli.md). +You can use Dev Environments through the intuitive GUI in Docker Desktop Dashboard or straight from your terminal with the new [`docker dev` CLI plugin](dev-cli.md). ## Use Dev Environments @@ -25,7 +25,7 @@ To use Dev Environments: 2. On the **Beta** tab, select **Turn on Dev Environments**. 3. Select **Apply & restart**. -The Dev Environments tab is now visible in Docker Dashboard. +The Dev Environments tab is now visible in Docker Desktop Dashboard. ## How does it work? diff --git a/content/manuals/desktop/faqs/linuxfaqs.md b/content/manuals/desktop/faqs/linuxfaqs.md index e7a809d4cfc..c0761110e0a 100644 --- a/content/manuals/desktop/faqs/linuxfaqs.md +++ b/content/manuals/desktop/faqs/linuxfaqs.md @@ -94,7 +94,7 @@ Docker Desktop stores Linux containers and images in a single, large "disk image #### Where is the disk image file? -To locate the disk image file, select **Settings** from the Docker Dashboard then **Advanced** from the **Resources** tab. +To locate the disk image file, select **Settings** from the Docker Desktop Dashboard then **Advanced** from the **Resources** tab. The **Advanced** tab displays the location of the disk image. It also displays the maximum size of the disk image and the actual space the disk image is consuming. Note that other tools might display space usage of the file in terms of the maximum file size, and not the actual file size. @@ -172,7 +172,7 @@ In this example, the actual size of the disk is `2333548` KB, whereas the maximu To reduce the maximum size of the disk image file: -1. From Docker Dashboard select **Settings** then **Advanced** from the **Resources** tab. +1. From Docker Desktop Dashboard select **Settings** then **Advanced** from the **Resources** tab. 2. The **Disk image size** section contains a slider that allows you to change the maximum size of the disk image. Adjust the slider to set a lower limit. diff --git a/content/manuals/desktop/faqs/macfaqs.md b/content/manuals/desktop/faqs/macfaqs.md index 763f1f06cc3..b0730d96ce4 100644 --- a/content/manuals/desktop/faqs/macfaqs.md +++ b/content/manuals/desktop/faqs/macfaqs.md @@ -45,7 +45,7 @@ Docker Desktop stores Linux containers and images in a single, large "disk image #### Where is the disk image file? -To locate the disk image file, select **Settings** from the Docker Dashboard then **Advanced** from the **Resources** tab. +To locate the disk image file, select **Settings** from the Docker Desktop Dashboard then **Advanced** from the **Resources** tab. The **Advanced** tab displays the location of the disk image. It also displays the maximum size of the disk image and the actual space the disk image is consuming. Note that other tools might display space usage of the file in terms of the maximum file size, and not the actual file size. diff --git a/content/manuals/desktop/faqs/releases.md b/content/manuals/desktop/faqs/releases.md index a8e1d3ed5d1..ed4cf4ed76e 100644 --- a/content/manuals/desktop/faqs/releases.md +++ b/content/manuals/desktop/faqs/releases.md @@ -10,7 +10,7 @@ tags: [FAQ] New releases are available roughly every month, unless there are critical fixes that need to be released sooner. -The **Automatically check for updates** setting in the **Software updates** tab is turned on by default. This means you receive notifications in the Docker menu and a notification badge on the Docker Dashboard when a new version is available. +The **Automatically check for updates** setting in the **Software updates** tab is turned on by default. This means you receive notifications in the Docker menu and a notification badge on the Docker Desktop Dashboard when a new version is available. You can also let Docker Desktop automatically download new updates in the background by selecting the **Always download updates** checkbox. diff --git a/content/manuals/desktop/feedback.md b/content/manuals/desktop/feedback.md index 298205c6c31..c0154b54377 100644 --- a/content/manuals/desktop/feedback.md +++ b/content/manuals/desktop/feedback.md @@ -10,7 +10,7 @@ There are many ways you can provide feedback on Docker Desktop or Docker Desktop ### In-product feedback -On each Docker Dashboard view, there is a **Give feedback** link. This sends you to a Google feedback form where you can share your feedback and ideas. +On each Docker Desktop Dashboard view, there is a **Give feedback** link. This sends you to a Google feedback form where you can share your feedback and ideas. You can also use the `docker feedback` command to submit feedback directly from the command line. diff --git a/content/manuals/desktop/kubernetes.md b/content/manuals/desktop/kubernetes.md index feee5c7eb44..7cf2c7121c1 100644 --- a/content/manuals/desktop/kubernetes.md +++ b/content/manuals/desktop/kubernetes.md @@ -20,7 +20,7 @@ workloads. ## Install and turn on Kubernetes -1. From the Docker Dashboard, select the **Settings**. +1. From the Docker Desktop Dashboard, select the **Settings**. 2. Select **Kubernetes** from the left sidebar. 3. Next to **Enable Kubernetes**, select the checkbox. 4. Select **Apply & Restart** to save the settings and then select **Install** to confirm. This instantiates images required to run the Kubernetes server as containers, and installs the `/usr/local/bin/kubectl` command on your machine. @@ -31,7 +31,7 @@ workloads. By default, Kubernetes containers are hidden from commands like `docker ps`, because managing them manually is not supported. Most users do not need this option. To see these internal containers, select **Show system containers (advanced)**. -When Kubernetes is turned on and running, an additional status bar in the Docker Dashboard footer and Docker menu displays. +When Kubernetes is turned on and running, an additional status bar in the Docker Desktop Dashboard footer and Docker menu displays. > [!NOTE] > @@ -76,7 +76,7 @@ For more information about `kubectl`, see the ## Turn off and uninstall Kubernetes To turn off Kubernetes in Docker Desktop: -1. From the Docker Dashboard, select the **Settings** icon. +1. From the Docker Desktop Dashboard, select the **Settings** icon. 2. Select **Kubernetes** from the left sidebar. 3. Next to **Enable Kubernetes**, clear the checkbox 4. Select **Apply & Restart** to save the settings.This stops and removes Kubernetes containers, and also removes the `/usr/local/bin/kubectl` command. diff --git a/content/manuals/desktop/release-notes.md b/content/manuals/desktop/release-notes.md index 372ab1f9092..5db73da4848 100644 --- a/content/manuals/desktop/release-notes.md +++ b/content/manuals/desktop/release-notes.md @@ -508,7 +508,7 @@ This can be resolved by adding the user to the **docker-users** group. Before st - Removed non-official Docker image used for Rust cross-compilation. - The maximum number of files per [Synchronized file share](synchronized-file-sharing.md) now exceeds 2 million. - Fixed an issue that caused the warning: "_The value provided to Autocomplete is invalid._" when selecting the **Export to local image** field. -- **Run Cloud** can now be accessed from the Docker Dashboard. +- **Run Cloud** can now be accessed from the Docker Desktop Dashboard. - Opting out from sending analytics will now also disable collecting data for bug reports. - You can now share and unshare a port to the Cloud Engine in the **Containers** view. - Shared cloud can now be accessed from the footer in the right-hand side of the **Dashboard**. @@ -967,7 +967,7 @@ This can be resolved by adding the user to the **docker-users** group. Before st #### For Windows -- Fixed a bug on Docker Desktop for Windows where the Docker Dashboard wouldn't display container logs correctly. Fixes [docker/for-win#13714](https://github.com/docker/for-win/issues/13714). +- Fixed a bug on Docker Desktop for Windows where the Docker Desktop Dashboard wouldn't display container logs correctly. Fixes [docker/for-win#13714](https://github.com/docker/for-win/issues/13714). ## 4.24.0 @@ -975,10 +975,10 @@ This can be resolved by adding the user to the **docker-users** group. Before st ### New -- The new Notification center is now available to all users so you can be notified of new releases, installation progress updates, and more. Select the bell icon in the bottom-right corner of the Docker Dashboard to access the notification center. +- The new Notification center is now available to all users so you can be notified of new releases, installation progress updates, and more. Select the bell icon in the bottom-right corner of the Docker Desktop Dashboard to access the notification center. - Compose Watch is now available to all users. For more information, see [Use Compose Watch](/manuals/compose/how-tos/file-watch.md). - Resource Saver is now available to all users and is enabled by default. To configure this feature, navigate to the **Resources** tab in **Settings**. For more information see [Docker Desktop's Resource Saver mode](use-desktop/resource-saver.md). -- You can now view and manage the Docker Engine state, with pause, stop, and resume, directly from the Docker Dashboard. +- You can now view and manage the Docker Engine state, with pause, stop, and resume, directly from the Docker Desktop Dashboard. ### Upgrades @@ -1071,7 +1071,7 @@ This can be resolved by adding the user to the **docker-users** group. Before st - Enroll an organization with Docker scout with `docker scout enroll`. - Stop, analyze, and compare local file systems with `docker scout cves --type fs`. - Fixed a bug where `docker stats` would hang when Docker Desktop was in Resource Saver mode. -- Fixed a bug where turning off experimental features via **Settings** in the Docker Dashboard would not fully turn off Resource Saver mode. +- Fixed a bug where turning off experimental features via **Settings** in the Docker Desktop Dashboard would not fully turn off Resource Saver mode. - Fixed a bug where the **Containers list** action button was clipped. - containerd image store: - Fixed `failed to read config content` error when interacting with some images. @@ -1591,7 +1591,7 @@ This can be resolved by adding the user to the **docker-users** group. Before st - Fixed a bug where the user is prompted for new HTTP proxy credentials repeatedly until Docker Desktop is restarted. - Added a diagnostics command `com.docker.diagnose login` to check HTTP proxy configuration. - Fixed actions on compose stack not working properly. Fixes [docker/for-mac#6566](https://github.com/docker/for-mac/issues/6566). -- Fixed the Docker dashboard trying at startup to get disk usage information and display an error banner before the engine was running. +- Fixed the Docker Desktop Dashboard trying at startup to get disk usage information and display an error banner before the engine was running. - Added an informational banner with instructions on how to opt-out of experimental feature access next to all experimental features. - Docker Desktop now supports downloading Kubernetes images via an HTTP proxy. - Fixed tooltips to not block action buttons. Fixes [docker/for-mac#6516](https://github.com/docker/for-mac/issues/6516). @@ -1631,7 +1631,7 @@ This can be resolved by adding the user to the **docker-users** group. Before st - Docker Desktop for Mac no longer needs to install the privileged helper process `com.docker.vmnetd` on install or on the first run. For more information see [Permission requirements for Mac](https://docs.docker.com/desktop/mac/permission-requirements/). - Added [WebAssembly capabilities](wasm/_index.md). Use with the [containerd integration](containerd/_index.md). - Improved the descriptions for beta and experimental settings to clearly explain the differences and how people can access them. -- Available disk space of VM now displays in the footer of Docker Dashboard for Mac and Linux. +- Available disk space of VM now displays in the footer of Docker Desktop Dashboard for Mac and Linux. - A disk space warning now displays in the footer if available space is below 3GB. - Changes to Docker Desktop's interface as we become more ADA accessible and visually unified. - Added a **Build** tab inside **Extensions** which contains all the necessary resources to build an extension. @@ -2085,7 +2085,7 @@ This can be resolved by adding the user to the **docker-users** group. Before st ### New - Added additional guides on the homepage for: Elasticsearch, MariaDB, Memcached, MySQL, RabbitMQ and Ubuntu. -- Added a footer to the Docker Dashboard with general information about the Docker Desktop update status and Docker Engine statistics +- Added a footer to the Docker Desktop Dashboard with general information about the Docker Desktop update status and Docker Engine statistics - Re-designed the containers table, adding: - A button to copy a container ID to the clipboard - A pause button for each container @@ -2108,7 +2108,7 @@ This can be resolved by adding the user to the **docker-users** group. Before st - Fixed an issue which caused Docker Desktop to hang if you quit the app whilst Docker Desktop was paused. - Fixed the Kubernetes cluster not resetting properly after the PKI expires. - Fixed an issue where the Extensions Marketplace was not using the defined http proxies. -- Improved the logs search functionality in Docker Dashboard to allow spaces. +- Improved the logs search functionality in Docker Desktop Dashboard to allow spaces. - Middle-button mouse clicks on buttons in the Dashboard now behave as a left-button click instead of opening a blank window. #### For Mac @@ -2307,7 +2307,7 @@ This can be resolved by adding the user to the **docker-users** group. Before st #### For all platforms -- The Docker Dashboard Volume Management feature now offers the ability to efficiently clean up volumes using multi-select checkboxes. +- The Docker Desktop Dashboard Volume Management feature now offers the ability to efficiently clean up volumes using multi-select checkboxes. #### For Mac @@ -2378,7 +2378,7 @@ This can be resolved by adding the user to the **docker-users** group. Before st #### For Windows - Fixed an issue that caused new installations to default to the Hyper-V backend instead of WSL 2. -- Fixed a crash in the Docker Dashboard which would make the systray menu disappear. +- Fixed a crash in the Docker Desktop Dashboard which would make the systray menu disappear. If you are running Docker Desktop on Windows Home, installing 4.5.1 will switch it back to WSL 2 automatically. If you are running another version of Windows, and you want Docker Desktop to use the WSL 2 backend, you must manually switch by enabling the **Use the WSL 2 based engine** option in the **Settings > General** section. Alternatively, you can edit the Docker Desktop settings file located at `%APPDATA%\Docker\settings.json` and manually switch the value of the `wslEngineEnabled` field to `true`. @@ -2416,7 +2416,7 @@ Alternatively, you can edit the Docker Desktop settings file located at `%APPDAT #### For Mac - Fixed an issue that caused the VM to become unresponsive during startup when using `osxfs` and when no host directories are shared with the VM. -- Fixed an issue that didn't allow users to stop a Docker Compose application using Docker Dashboard if the application was started in a different version of Docker Compose. For example, if the user started a Docker Compose application in V1 and then switched to Docker Compose V2, attempts to stop the Docker Compose application would fail. +- Fixed an issue that didn't allow users to stop a Docker Compose application using Docker Desktop Dashboard if the application was started in a different version of Docker Compose. For example, if the user started a Docker Compose application in V1 and then switched to Docker Compose V2, attempts to stop the Docker Compose application would fail. - Fixed an issue where Docker Desktop incorrectly prompted users to sign in after they quit Docker Desktop and start the application. - Fixed an issue where the **About Docker Desktop** window wasn't working anymore. - Limit the number of CPUs to 8 on Mac M1 to fix the startup problem. Fixes [docker/for-mac#6063](https://github.com/docker/for-mac/issues/6063). @@ -2598,7 +2598,7 @@ CVE-2021-44228](https://www.docker.com/blog/apache-log4j-2-cve-2021-44228/). ### Known issue -Docker Dashboard incorrectly displays the container memory usage as zero on +Docker Desktop Dashboard incorrectly displays the container memory usage as zero on Hyper-V based machines. You can use the [`docker stats`](/reference/cli/docker/container/stats.md) command on the command line as a workaround to view the @@ -2624,7 +2624,7 @@ actual memory usage. See - Ships [Docker Public Roadmap#228](https://github.com/docker/roadmap/issues/228) -**Window management**: The Docker Dashboard window size and position persists when you close and reopen Docker Desktop. +**Window management**: The Docker Desktop Dashboard window size and position persists when you close and reopen Docker Desktop. ### Upgrades @@ -2640,7 +2640,7 @@ actual memory usage. See #### For all platforms - Improved: Self-diagnose now also checks for overlap between host IPs and `docker networks`. -- Fixed the position of the indicator that displays the availability of an update on the Docker Dashboard. +- Fixed the position of the indicator that displays the availability of an update on the Docker Desktop Dashboard. #### For Mac @@ -2667,7 +2667,7 @@ actual memory usage. See > When upgrading from 4.1.0, the Docker menu does not change to **Update and restart** so you can just wait for the download to complete (icon changes) and then select **Restart**. This bug is fixed in 4.1.1, for future upgrades. - Fixed a bug where a `Docker.qcow2` file would be ignored on upgrade and a fresh `Docker.raw` used instead, resulting in containers and images disappearing. If a system has both files (due to the previous bug), then the most recently modified file will be used to avoid recent containers and images disappearing again. To force the use of the old `Docker.qcow2`, delete the newer `Docker.raw` file. Fixes [docker/for-mac#5998](https://github.com/docker/for-mac/issues/5998). -- Fixed the update notification overlay sometimes getting out of sync between the **Settings** button and the **Software update** button in the Docker Dashboard. +- Fixed the update notification overlay sometimes getting out of sync between the **Settings** button and the **Software update** button in the Docker Desktop Dashboard. - Fixed the menu entry to install a newly downloaded Docker Desktop update. When an update is ready to install, the **Restart** option changes to **Update and restart**. #### For Windows @@ -2729,7 +2729,7 @@ Docker Desktop may fail to start when upgrading to 4.1.0 on some WSL-based distr #### For all platforms -- Fixed a bug where copy-paste was not available in the Docker Dashboard. +- Fixed a bug where copy-paste was not available in the Docker Desktop Dashboard. #### For Windows diff --git a/content/manuals/desktop/settings.md b/content/manuals/desktop/settings.md index 4dd41b4c4e8..732f8ee2570 100644 --- a/content/manuals/desktop/settings.md +++ b/content/manuals/desktop/settings.md @@ -14,7 +14,7 @@ weight: 150 To navigate to **Settings** either: - Select the Docker menu {{< inline-image src="images/whale-x.svg" alt="whale menu" >}} and then **Settings** -- Select the **Settings** icon from the Docker Dashboard. +- Select the **Settings** icon from the Docker Desktop Dashboard. You can also locate the `settings.json` file at: - Mac: `~/Library/Group Containers/group.com.docker/settings.json` @@ -34,7 +34,7 @@ On the **General** tab, you can configure when to start Docker and specify other - **Choose theme for Docker Desktop**. Choose whether you want to apply a **Light** or **Dark** theme to Docker Desktop. Alternatively you can set Docker Desktop to **Use system settings**. - **Choose container terminal**. Determines which terminal is launched when opening the terminal from a container. -If you choose the integrated terminal, you can run commands in a running container straight from the Docker Dashboard. For more information, see [Explore containers](/manuals/desktop/use-desktop/container.md). +If you choose the integrated terminal, you can run commands in a running container straight from the Docker Desktop Dashboard. For more information, see [Explore containers](/manuals/desktop/use-desktop/container.md). - **Enable Docker terminal**. Interact with your host machine and execute commands directly from Docker Desktop. @@ -432,14 +432,14 @@ select the **Release Notes** option to learn what's included in the updated vers Turn off the check for updates by clearing the **Automatically check for updates** check box. This disables notifications in the Docker menu and the notification -badge that appears on the Docker Dashboard. To check for updates manually, select +badge that appears on the Docker Desktop Dashboard. To check for updates manually, select the **Check for updates** option in the Docker menu. To allow Docker Desktop to automatically download new updates in the background, select **Always download updates**. This downloads newer versions of Docker Desktop when an update becomes available. After downloading the update, select **Apply and Restart** to install the update. You can do this either through the -Docker menu or in the **Updates** section in the Docker Dashboard. +Docker menu or in the **Updates** section in the Docker Desktop Dashboard. ## Extensions @@ -485,7 +485,7 @@ Use the **Notifications** tab to turn on or turn off notifications for the follo By default, all notifications are turned on. You'll always receive error notifications and notifications about new Docker Desktop releases and updates. -Notifications momentarily appear in the lower-right of the Docker Dashboard and then move to the **Notifications** drawer. To open the **Notifications** drawer, select {{< inline-image src="images/notifications.svg" alt="notifications" >}}. +Notifications momentarily appear in the lower-right of the Docker Desktop Dashboard and then move to the **Notifications** drawer. To open the **Notifications** drawer, select {{< inline-image src="images/notifications.svg" alt="notifications" >}}. ## Advanced diff --git a/content/manuals/desktop/synchronized-file-sharing.md b/content/manuals/desktop/synchronized-file-sharing.md index 74791d47a0b..6651a8b71f3 100644 --- a/content/manuals/desktop/synchronized-file-sharing.md +++ b/content/manuals/desktop/synchronized-file-sharing.md @@ -43,7 +43,7 @@ To create a file share instance: 3. In the **Synchronized File Shares** section, select the **Create share** icon. 4. Select a host folder to share. The synchronized file share should initialize and be usable. -File shares take a few seconds to initialize as files are copied into the Docker Desktop VM. During this time, the status indicator displays **Preparing**. There is also a status icon in the footer of the Docker Dashboard that keeps you updated. +File shares take a few seconds to initialize as files are copied into the Docker Desktop VM. During this time, the status indicator displays **Preparing**. There is also a status icon in the footer of the Docker Desktop Dashboard that keeps you updated. When the status indicator displays **Watching for filesystem changes**, your files are available to the VM through all the standard bind mount mechanisms, whether that's `-v` in the command line or specified in your `compose.yml` file. diff --git a/content/manuals/desktop/uninstall.md b/content/manuals/desktop/uninstall.md index 17f1e83bb59..b7c7b1cab77 100644 --- a/content/manuals/desktop/uninstall.md +++ b/content/manuals/desktop/uninstall.md @@ -54,7 +54,7 @@ C:\Users\\.docker To uninstall Docker Desktop from your Mac: -1. From the Docker menu, select the **Troubleshoot** icon in the top-right corner of Docker Dashboard and then select **Uninstall**. +1. From the Docker menu, select the **Troubleshoot** icon in the top-right corner of the Docker Desktop Dashboard and then select **Uninstall**. 2. Select **Uninstall** to confirm your selection. You can also uninstall Docker Desktop from the CLI. Run: diff --git a/content/manuals/desktop/use-desktop/_index.md b/content/manuals/desktop/use-desktop/_index.md index c3a6697759a..70d13dcf225 100644 --- a/content/manuals/desktop/use-desktop/_index.md +++ b/content/manuals/desktop/use-desktop/_index.md @@ -1,6 +1,6 @@ --- -description: Learn how to use the Docker Dashboard within Docker Desktop, including Quick search, the Docker menu, and more -keywords: Docker Dashboard, manage, containers, gui, dashboard, images, user manual, +description: Learn how to use the Docker Desktop Dashboard within Docker Desktop, including Quick search, the Docker menu, and more +keywords: Docker Desktop Dashboard, manage, containers, gui, dashboard, images, user manual, whale menu title: Explore Docker Desktop weight: 30 @@ -8,9 +8,9 @@ aliases: - /desktop/dashboard/ --- -When you open Docker Desktop, the Docker Dashboard displays. +When you open Docker Desktop, the Docker Desktop Dashboard displays. -![Docker Dashboard on Containers view](../images/dashboard.webp) +![Docker Desktop Dashboard on Containers view](../images/dashboard.webp) The **Containers** view provides a runtime view of all your containers and applications. It allows you to interact with containers and applications, and manage the lifecycle of your applications directly from your machine. This view also provides an intuitive interface to perform common actions to inspect, interact with, and manage your Docker objects including containers and Docker Compose-based applications. For more information, see [Explore running containers and applications](container.md). @@ -20,11 +20,11 @@ The **Volumes** view displays a list of volumes and allows you to easily create The **Builds** view lets you inspect your build history and manage builders. By default, it displays a list of all your ongoing and completed builds. [Explore builds](builds.md). -In addition, the Docker Dashboard allows you to: +In addition, the Docker Desktop Dashboard let you: - Navigate to the **Settings** menu to configure your Docker Desktop settings. Select the **Settings** icon in the Dashboard header. - Access the **Troubleshoot** menu to debug and perform restart operations. Select the **Troubleshoot** icon in the Dashboard header. -- Be notified of new releases, installation progress updates, and more in the **Notifications center**. Select the bell icon in the bottom-right corner of the Docker Dashboard to access the notification center. +- Be notified of new releases, installation progress updates, and more in the **Notifications center**. Select the bell icon in the bottom-right corner of the Docker Desktop Dashboard to access the notification center. - Access the **Learning center** from the Dashboard header. It helps you get started with quick in-app walkthroughs and provides other resources for learning about Docker. For a more detailed guide about getting started, see [Get started](/get-started/introduction/_index.md). @@ -33,7 +33,7 @@ In addition, the Docker Dashboard allows you to: ## Quick search -From the Docker Dashboard you can use Quick Search, which is located in the Dashboard header, to search for: +From the Docker Desktop Dashboard you can use Quick Search, which is located in the Dashboard header, to search for: - Any container or Compose application on your local system. You can see an overview of associated environment variables or perform quick actions, such as start, stop, or delete. @@ -51,7 +51,7 @@ Docker Desktop also provides an easy-access tray icon that appears in the taskba To display the Docker menu, select the {{< inline-image src="../../assets/images/whale-x.svg" alt="whale menu" >}} icon. It displays the following options: -- **Dashboard**. This takes you to the Docker Dashboard. +- **Dashboard**. This takes you to the Docker Desktop Dashboard. - **Sign in/Sign up** - **Settings** - **Check for updates** diff --git a/content/manuals/desktop/use-desktop/builds.md b/content/manuals/desktop/use-desktop/builds.md index 3743d259dad..4d0b066dd35 100644 --- a/content/manuals/desktop/use-desktop/builds.md +++ b/content/manuals/desktop/use-desktop/builds.md @@ -23,7 +23,7 @@ connected to the same cloud builder. ## Show build list -Select the **Builds** view in the Docker Dashboard to open the build list. +Select the **Builds** view in the Docker Desktop Dashboard to open the build list. The build list shows your completed and ongoing builds. The **Build history** tab shows completed historical builds, and from here you can inspect the build diff --git a/content/manuals/desktop/use-desktop/container.md b/content/manuals/desktop/use-desktop/container.md index 8e9de4c84b5..a4f59be747e 100644 --- a/content/manuals/desktop/use-desktop/container.md +++ b/content/manuals/desktop/use-desktop/container.md @@ -69,7 +69,7 @@ Using the integrated terminal is the same as running one of the following comman The integrated terminal: - Persists your session and **Debug mode** setting if you navigate to another - part of the Docker Dashboard and then return. + part of the Docker Desktop Dashboard and then return. - Supports copy, paste, search, and clearing your session. - When not using debug mode, it automatically detects the default user for a running container from the image's Dockerfile. If no user is specified, or diff --git a/content/manuals/desktop/use-desktop/pause.md b/content/manuals/desktop/use-desktop/pause.md index 5fc1a334135..22bf1b67124 100644 --- a/content/manuals/desktop/use-desktop/pause.md +++ b/content/manuals/desktop/use-desktop/pause.md @@ -1,6 +1,6 @@ --- -description: understand what pausing Docker Dashboard means -keywords: Docker Dashboard, manage, containers, gui, dashboard, pause, user manual +description: understand what pausing Docker Desktop Dashboard means +keywords: Docker Desktop Dashboard, manage, containers, gui, dashboard, pause, user manual title: Pause Docker Desktop weight: 60 --- @@ -9,7 +9,7 @@ When Docker Desktop is paused, the Linux VM running Docker Engine is paused, the You can manually pause Docker Desktop by selecting the Docker menu {{< inline-image src="../images/whale-x.svg" alt="whale menu" >}} and then **Pause**. To manually resume Docker Desktop, select the **Resume** option in the Docker menu, or run any Docker CLI command. -When you manually pause Docker Desktop, a paused status displays on the Docker menu and on the Docker Dashboard. You can still access the **Settings** and the **Troubleshoot** menu. +When you manually pause Docker Desktop, a paused status displays on the Docker menu and on the Docker Desktop Dashboard. You can still access the **Settings** and the **Troubleshoot** menu. >**Tip** > diff --git a/content/manuals/desktop/use-desktop/volumes.md b/content/manuals/desktop/use-desktop/volumes.md index eaf5dcb9063..0b045ba705c 100644 --- a/content/manuals/desktop/use-desktop/volumes.md +++ b/content/manuals/desktop/use-desktop/volumes.md @@ -1,12 +1,12 @@ --- description: Understand what you can do with the Volumes view on Docker Dashboard -keywords: Docker Dashboard, manage, containers, gui, dashboard, volumes, user manual +keywords: Docker Desktop Dashboard, manage, containers, gui, dashboard, volumes, user manual title: Explore the Volumes view in Docker Desktop linkTitle: Volumes weight: 30 --- -The **Volumes** view in Docker Dashboard lets you create, delete, and perform +The **Volumes** view in Docker Desktop Dashboard lets you create, delete, and perform other actions on your [volumes](/manuals/engine/storage/volumes.md). You can also see which volumes are being used as well as inspect the files and folders in your volumes. diff --git a/content/manuals/extensions/extensions-sdk/architecture/_index.md b/content/manuals/extensions/extensions-sdk/architecture/_index.md index 2e7ae140add..d3dde080303 100644 --- a/content/manuals/extensions/extensions-sdk/architecture/_index.md +++ b/content/manuals/extensions/extensions-sdk/architecture/_index.md @@ -9,7 +9,7 @@ weight: 50 --- Extensions are applications that run inside the Docker Desktop. They're packaged as Docker images, distributed -through Docker Hub, and installed by users either through the Marketplace within Docker Dashboard or the +through Docker Hub, and installed by users either through the Marketplace within the Docker Desktop Dashboard or the Docker Extensions CLI. Extensions can be composed of three (optional) components: diff --git a/content/manuals/extensions/extensions-sdk/build/backend-extension-tutorial.md b/content/manuals/extensions/extensions-sdk/build/backend-extension-tutorial.md index 687576ce026..8f9126c564c 100644 --- a/content/manuals/extensions/extensions-sdk/build/backend-extension-tutorial.md +++ b/content/manuals/extensions/extensions-sdk/build/backend-extension-tutorial.md @@ -345,14 +345,14 @@ Once built, you need to update it, or install it if you haven't already done so. docker extension update awesome-inc/my-extension:latest ``` -Now you can see the backend service running in the **Containers8* tab of the Docker Dashboard and watch the logs when you need to debug it. +Now you can see the backend service running in the **Containers** view of the Docker Desktop Dashboard and watch the logs when you need to debug it. > [!TIP] > > You may need to turn on the **Show system containers** option in **Settings** to see the backend container running. > See [Show extension containers](../dev/test-debug.md#show-the-extension-containers) for more information. -Open Docker Dashboard and select the **Containers** tab. You should see the response from the backend service +Open the Docker Desktop Dashboard and select the **Containers** tab. You should see the response from the backend service call displayed. ## What's next? diff --git a/content/manuals/extensions/extensions-sdk/build/minimal-frontend-extension.md b/content/manuals/extensions/extensions-sdk/build/minimal-frontend-extension.md index 9d9bf42995a..f530852907c 100644 --- a/content/manuals/extensions/extensions-sdk/build/minimal-frontend-extension.md +++ b/content/manuals/extensions/extensions-sdk/build/minimal-frontend-extension.md @@ -95,7 +95,7 @@ $ docker extension install awesome-inc/my-extension:latest ## Preview the extension -To preview the extension in Docker Desktop, close and open Docker Dashboard once the installation is complete. +To preview the extension in Docker Desktop, close and open the Docker Desktop Dashboard once the installation is complete. The left-hand menu displays a new tab with the name of your extension. diff --git a/content/manuals/extensions/extensions-sdk/dev/continuous-integration.md b/content/manuals/extensions/extensions-sdk/dev/continuous-integration.md index 5fa76483296..1c33ca15e51 100644 --- a/content/manuals/extensions/extensions-sdk/dev/continuous-integration.md +++ b/content/manuals/extensions/extensions-sdk/dev/continuous-integration.md @@ -55,7 +55,7 @@ beforeAll(async () => { }); ``` -Then open the Docker Dashboard and run some tests in your extension's UI: +Then open the Docker Desktop Dashboard and run some tests in your extension's UI: ```ts describe("Test my extension", () => { @@ -70,7 +70,7 @@ describe("Test my extension", () => { }); ``` -Finally, close the Docker Dashboard and uninstall your extension: +Finally, close the Docker Desktop Dashboard and uninstall your extension: ```ts afterAll(async () => { diff --git a/content/manuals/extensions/marketplace.md b/content/manuals/extensions/marketplace.md index 9135220cf23..4683e7a58d7 100644 --- a/content/manuals/extensions/marketplace.md +++ b/content/manuals/extensions/marketplace.md @@ -25,7 +25,7 @@ Self-published extensions are autonomously published by extension developers and To install an extension: 1. Open Docker Desktop. -2. From the Docker Dashboard, select the **Extensions** tab. +2. From the Docker Desktop Dashboard, select the **Extensions** tab. The Extensions Marketplace opens on the **Browse** tab. 3. Browse the available extensions. You can sort the list of extensions by **Recently added**, **Most installed**, or alphabetically. Alternatively, use the **Content** or **Categories** drop-down menu to search for extensions by whether they have been reviewed or not, or by category. @@ -35,7 +35,7 @@ From here, you can select **Open** to access the extension or install additional ## Update an extension -You can update any extension outside of Docker Desktop releases. To update an extension to the latest version, navigate to the Docker Dashboard and select the **Manage** tab. +You can update any extension outside of Docker Desktop releases. To update an extension to the latest version, navigate to the Docker Desktop Dashboard and select the **Manage** tab. The **Manage** tab displays with all your installed extensions. If an extension has a new version available, it displays an **Update** button. @@ -48,7 +48,7 @@ You can uninstall an extension at any time. > > Any data used by the extension that's stored in a volume must be manually deleted. -1. Navigate to the Docker Dashboard and select the **Manage** tab. +1. Navigate to the Docker Desktop Dashboard and select the **Manage** tab. This displays a list of extensions you've installed. 2. Select the ellipsis to the right of extension you want to uninstall. 3. Select **Uninstall**. diff --git a/content/manuals/extensions/non-marketplace.md b/content/manuals/extensions/non-marketplace.md index 19d8af5e8ad..9f7de62fd34 100644 --- a/content/manuals/extensions/non-marketplace.md +++ b/content/manuals/extensions/non-marketplace.md @@ -28,7 +28,7 @@ To install an extension which is not present in the Marketplace, you can use the In a terminal, type `docker extension install IMAGE[:TAG]` to install an extension by its image reference and optionally a tag. Use the `-f` or `--force` flag to avoid interactive confirmation. -Go to the Docker Dashboard to see the new extension installed. +Go to the Docker Desktop Dashboard to see the new extension installed. ## List installed extensions @@ -41,7 +41,7 @@ ID PROVIDER VERSION UI john/my-extension John latest 1 tab(My-Extension) Running(1) - ``` -Go to the Docker Dashboard, click on **Add Extensions** and on the **Managed** tab to see the new extension installed. +Go to the Docker Desktop Dashboard, select **Add Extensions** and on the **Managed** tab to see the new extension installed. Notice that an `UNPUBLISHED` label displays which indicates that the extension has not been installed from the Marketplace. ## Update an extension @@ -49,7 +49,7 @@ Notice that an `UNPUBLISHED` label displays which indicates that the extension h To update an extension which isn't present in the Marketplace, in a terminal type `docker extension update IMAGE[:TAG]` where the `TAG` should be different from the extension that's already installed. For instance, if you installed an extension with `docker extension install john/my-extension:0.0.1`, you can update it by running `docker extension update john/my-extension:0.0.2`. -Go to the Docker Dashboard to see the new extension updated. +Go to the Docker Desktop Dashboard to see the new extension updated. > [!NOTE] > diff --git a/content/manuals/extensions/settings-feedback.md b/content/manuals/extensions/settings-feedback.md index de9e2db07a5..d233d19e5d2 100644 --- a/content/manuals/extensions/settings-feedback.md +++ b/content/manuals/extensions/settings-feedback.md @@ -39,7 +39,7 @@ You can install extensions through the Marketplace or through the Extensions SDK ### See containers created by extensions -By default, containers created by extensions are hidden from the list of containers in Docker Dashboard and the Docker CLI. To make them visible +By default, containers created by extensions are hidden from the list of containers in the Docker Desktop Dashboard and the Docker CLI. To make them visible update your settings: 1. Navigate to **Settings**. @@ -57,7 +57,7 @@ update your settings: Feedback can be given to an extension author through a dedicated Slack channel or GitHub. To submit feedback about a particular extension: -1. Navigate to Docker Dashboard and select the **Manage** tab. +1. Navigate to the Docker Desktop Dashboard and select the **Manage** tab. This displays a list of extensions you've installed. 2. Select the extension you want to provide feedback on. 3. Scroll down to the bottom of the extension's description and, depending on the diff --git a/content/manuals/harmonia/_index.md b/content/manuals/harmonia/_index.md index ed42d508910..60d33f1b4bb 100644 --- a/content/manuals/harmonia/_index.md +++ b/content/manuals/harmonia/_index.md @@ -22,7 +22,7 @@ To get started with Project Harmonia, you need to: ## Quickstart -You can use Project Harmonia from the Docker Dashboard or from the CLI. +You can use Project Harmonia from the Docker Desktop Dashboard or from the CLI. This guide introduces you to essential commands and steps for creating, managing, and sharing a cloud engine. @@ -31,7 +31,7 @@ This guide introduces you to essential commands and steps for creating, managing {{< tabs group="method" >}} {{< tab name="Docker Desktop">}} -1. In the Docker Dashboard, navigate to the **Project Harmonia** tab. +1. In the Docker Desktop Dashboard, navigate to the **Project Harmonia** tab. 2. In the top right-hand corner, select **Create Cloud Engine**. 3. Fill out the creation form: - Enter `cloudengine` as the name @@ -41,7 +41,7 @@ This guide introduces you to essential commands and steps for creating, managing Note that the **Switch Docker Context to use remote engine** is selected by default. The automatically switches you to your new cloud engine once it has been created. 4. Select **Create**. -To verify creation, check the context switcher in the top-left corner of the Docker Dashboard; it should display `cloudengine`. You’re now ready to use it. +To verify creation, check the context switcher in the top-left corner of the Docker Desktop Dashboard; it should display `cloudengine`. You’re now ready to use it. {{< /tab >}} {{< tab name="CLI">}} @@ -92,7 +92,7 @@ You should see the following: This maps the container's port `80` to the host's port `8080`. If port `8080` is already in use on your host, you can specify a different port. 2. View the Nginx welcome page. Navigate to [`http://localhost:8080/`](http://localhost:8080/). 3. Verify the running container: - - In the **Containers** tab in the Docker Dashboard, you should see your Nginx container listed. + - In the **Containers** tab in the Docker Desktop Dashboard, you should see your Nginx container listed. - Alternatively, list all running containers in the cloud engine via the terminal: ```console $ docker ps @@ -110,7 +110,7 @@ Running a container with a cloud engine is just as straightforward as running it - Choose an organization to associate the cloud engine with - Select the **Standard** engine size with the **AMD-64** architecture In the **Project Harmonia** view you should now see both `cloudengine` and `cloudengine2`. -2. Switch between engines, also known as your Docker contexts. Use the context switcher in the top-left corner of the Docker Dashboard to toggle between your cloud engines or switch from your local engine (`desktop-linux`) to a cloud engine. +2. Switch between engines, also known as your Docker contexts. Use the context switcher in the top-left corner of the Docker Desktop Dashboard to toggle between your cloud engines or switch from your local engine (`desktop-linux`) to a cloud engine. {{< /tab >}} {{< tab name="CLI">}} @@ -140,7 +140,7 @@ Project Harmonia takes advantage of [Synchronized file shares](/manuals/desktop/ {{< tab name="Docker Desktop">}} 1. Clone the [Awesome Compose](https://github.com/docker/awesome-compose) repository. -2. In the Docker Dashboard, navigate to the **Project Harmonia** view. +2. In the Docker Desktop Dashboard, navigate to the **Project Harmonia** view. 3. For the `cloudengine` cloud engine, select the **Actions** menu and then **Manage file syncs**. 4. Select **Create file sync**. 5. Navigate to the `awesome-compose/react-express-mysql` folder and select **Open**. @@ -178,12 +178,12 @@ Project Harmonia takes advantage of [Synchronized file shares](/manuals/desktop/ {{< tab name="Docker Desktop">}} 1. Make sure your Docker context is set to `cloudengine`. -2. In the Docker Dashboard, navigate to the **Containers** view. +2. In the Docker Desktop Dashboard, navigate to the **Containers** view. 3. Select the **lock** icon in the **Ports** column of your running container next to `3000:3000`. This creates a publicly accessible URL that you can share with teammates. 4. Select the **copy** icon, to copy this URL. -To view all shared ports for your Docker context, select the **Shared ports** icon in the bottom-right corner of the Docker Dashboard. +To view all shared ports for your Docker context, select the **Shared ports** icon in the bottom-right corner of the Docker Desktop Dashboard. {{< /tab >}} {{< tab name="CLI">}}