From 14ab809d989e0ed98e2221bd25e371a5914fd9b9 Mon Sep 17 00:00:00 2001 From: Allie Sadler <102604716+aevesdocker@users.noreply.github.com> Date: Mon, 18 Jul 2022 14:38:03 +0100 Subject: [PATCH 1/6] merge dashboard and user manual --- _data/toc.yaml | 18 ++-- desktop/faqs/macfaqs.md | 165 +++++++++++++++++++++++++++++++ desktop/faqs/windowsfaqs.md | 74 ++++++++++++++ desktop/get-started.md | 134 +++++++++++++++++++++++++ desktop/use-desktop/container.md | 98 ++++++++++++++++++ desktop/use-desktop/images.md | 110 +++++++++++++++++++++ desktop/use-desktop/volumes.md | 32 ++++++ 7 files changed, 623 insertions(+), 8 deletions(-) create mode 100644 desktop/get-started.md create mode 100644 desktop/use-desktop/container.md create mode 100644 desktop/use-desktop/images.md create mode 100644 desktop/use-desktop/volumes.md diff --git a/_data/toc.yaml b/_data/toc.yaml index 1c511d5ba1a0..013e435001bf 100644 --- a/_data/toc.yaml +++ b/_data/toc.yaml @@ -1155,10 +1155,18 @@ manuals: title: Install on Ubuntu - path: /desktop/install/archlinux/ title: Install on Arch + - path: /desktop/get-started/ + title: Sign in and get started + - sectiontitle: Explore Docker Desktop + section: + - path: /desktop/use-desktop/containers/ + title: Explore Containers + - path: /desktop/use-desktop/images/ + title: Explore Images + - path: /desktop/use-desktop/volumes/ + title: Explore Volumes - sectiontitle: Mac section: - - path: /desktop/mac/ - title: User manual - path: /desktop/mac/troubleshoot/ title: Logs and troubleshooting - path: /desktop/mac/apple-silicon/ @@ -1167,20 +1175,14 @@ manuals: title: Privileged Helper - sectiontitle: Windows section: - - path: /desktop/windows/ - title: User manual - path: /desktop/windows/troubleshoot/ title: Logs and troubleshooting - path: /desktop/windows/wsl/ title: Docker Desktop WSL 2 backend - sectiontitle: Linux section: - - path: /desktop/linux/ - title: User manual - path: /desktop/linux/troubleshoot/ title: Logs and troubleshooting - - path: /desktop/dashboard/ - title: Dashboard - sectiontitle: Change settings section: - path: /desktop/settings/mac/ diff --git a/desktop/faqs/macfaqs.md b/desktop/faqs/macfaqs.md index a17fce91fc00..5472cfe9f8ca 100644 --- a/desktop/faqs/macfaqs.md +++ b/desktop/faqs/macfaqs.md @@ -118,3 +118,168 @@ To reduce the maximum size of the disk image file: When you reduce the maximum size, the current disk image file is deleted, and therefore, all containers and images will be lost. +### How do I add TLS certificates? + +You can add trusted Certificate Authorities (CAs) (used to verify registry +server certificates) and client certificates (used to authenticate to +registries) to your Docker daemon. + +#### Add custom CA certificates (server side) + +All trusted CAs (root or intermediate) are supported. Docker Desktop creates a +certificate bundle of all user-trusted CAs based on the Mac Keychain, and +appends it to Moby trusted certificates. So if an enterprise SSL certificate is +trusted by the user on the host, it is trusted by Docker Desktop. + +To manually add a custom, self-signed certificate, start by adding the +certificate to the macOS keychain, which is picked up by Docker Desktop. Here is +an example: + +```console +$ sudo security add-trusted-cert -d -r trustRoot -k /Library/Keychains/System.keychain ca.crt +``` + +Or, if you prefer to add the certificate to your own local keychain only (rather +than for all users), run this command instead: + +```console +$ security add-trusted-cert -d -r trustRoot -k ~/Library/Keychains/login.keychain ca.crt +``` + +See also, [Directory structures for +certificates](#directory-structures-for-certificates). + +> **Note**: You need to restart Docker Desktop after making any changes to the +> keychain or to the `~/.docker/certs.d` directory in order for the changes to +> take effect. +For a complete explanation of how to do this, see the blog post [Adding +Self-signed Registry Certs to Docker & Docker Desktop for +Mac](https://blog.container-solutions.com/adding-self-signed-registry-certs-docker-mac){:target="_blank" rel="noopener" class="_"}. + +#### Add client certificates + +You can put your client certificates in +`~/.docker/certs.d/:/client.cert` and +`~/.docker/certs.d/:/client.key`. + +When the Docker Desktop application starts, it copies the `~/.docker/certs.d` +folder on your Mac to the `/etc/docker/certs.d` directory on Moby (the Docker +Desktop `xhyve` virtual machine). + +> * You need to restart Docker Desktop after making any changes to the keychain +> or to the `~/.docker/certs.d` directory in order for the changes to take +> effect. +> +> * The registry cannot be listed as an _insecure registry_ (see [Docker +> Engine](../settings/mac-settings#docker-engine). Docker Desktop ignores certificates listed +> under insecure registries, and does not send client certificates. Commands +> like `docker run` that attempt to pull from the registry produce error +> messages on the command line, as well as on the registry. +#### Directory structures for certificates + +If you have this directory structure, you do not need to manually add the CA +certificate to your Mac OS system login: + +``` +/Users//.docker/certs.d/ +└── : + ├── ca.crt + ├── client.cert + └── client.key +``` + +The following further illustrates and explains a configuration with custom +certificates: + +``` +/etc/docker/certs.d/ <-- Certificate directory +└── localhost:5000 <-- Hostname:port + ├── client.cert <-- Client certificate + ├── client.key <-- Client key + └── ca.crt <-- Certificate authority that signed + the registry certificate +``` + +You can also have this directory structure, as long as the CA certificate is +also in your keychain. + +``` +/Users//.docker/certs.d/ +└── : + ├── client.cert + └── client.key +``` + +To learn more about how to install a CA root certificate for the registry and +how to set the client TLS certificate for verification, see +[Verify repository client with certificates](../../engine/security/certificates.md) +in the Docker Engine topics. + +### How do I install shell completion? + +Docker Desktop comes with scripts to enable completion for the `docker` and `docker-compose` commands. The completion scripts may be +found inside `Docker.app`, in the `Contents/Resources/etc/` directory and can be +installed both in Bash and Zsh. + +#### Bash + +Bash has [built-in support for +completion](https://www.debian-administration.org/article/316/An_introduction_to_bash_completion_part_1){:target="_blank" +class="_"} To activate completion for Docker commands, these files need to be +copied or symlinked to your `bash_completion.d/` directory. For example, if you +installed bash via [Homebrew](https://brew.sh): + +```bash +etc=/Applications/Docker.app/Contents/Resources/etc +ln -s $etc/docker.bash-completion $(brew --prefix)/etc/bash_completion.d/docker +ln -s $etc/docker-compose.bash-completion $(brew --prefix)/etc/bash_completion.d/docker-compose +``` + +Add the following to your `~/.bash_profile`: + +```bash +[ -f /usr/local/etc/bash_completion ] && . /usr/local/etc/bash_completion +``` + +OR + +```bash +if [ -f $(brew --prefix)/etc/bash_completion ]; then +. $(brew --prefix)/etc/bash_completion +fi +``` + +#### Zsh + +In Zsh, the [completion +system](http://zsh.sourceforge.net/Doc/Release/Completion-System.html){:target="_blank" rel="nooopener" class="_"} +takes care of things. To activate completion for Docker commands, +these files need to be copied or symlinked to your Zsh `site-functions/` +directory. For example, if you installed Zsh via [Homebrew](https://brew.sh){:target="_blank" rel="nooopener" class="_"}: + +```bash +etc=/Applications/Docker.app/Contents/Resources/etc +ln -s $etc/docker.zsh-completion /usr/local/share/zsh/site-functions/_docker +ln -s $etc/docker-compose.zsh-completion /usr/local/share/zsh/site-functions/_docker-compose +``` + +#### Fish-Shell + +Fish-shell also supports tab completion [completion +system](https://fishshell.com/docs/current/#tab-completion){:target="_blank" +class="_"}. To activate completion for Docker commands, +these files need to be copied or symlinked to your Fish-shell `completions/` +directory. + +Create the `completions` directory: + +```console +$ mkdir -p ~/.config/fish/completions +``` + +Now add fish completions from docker. + +```console +$ ln -shi /Applications/Docker.app/Contents/Resources/etc/docker.fish-completion ~/.config/fish/completions/docker.fish +$ ln -shi /Applications/Docker.app/Contents/Resources/etc/docker-compose.fish-completion ~/.config/fish/completions/docker-compose.fish +``` \ No newline at end of file diff --git a/desktop/faqs/windowsfaqs.md b/desktop/faqs/windowsfaqs.md index d2942cae6784..7590733d0651 100644 --- a/desktop/faqs/windowsfaqs.md +++ b/desktop/faqs/windowsfaqs.md @@ -61,3 +61,77 @@ The Windows native symlinks are visible within the containers as symlinks, where Docker Desktop mounts the Windows host filesystem under `/run/desktop` inside the container running Kubernetes. See the [Stack Overflow post](https://stackoverflow.com/questions/67746843/clear-persistent-volume-from-a-kubernetes-cluster-running-on-docker-desktop/69273405#69273){:target="_blank" rel="noopener" class="_"} for an example of how to configure a Kubernetes Persistent Volume to represent directories on the host. + +### How do I add custom CA certificates? + +You can add trusted **Certificate Authorities (CAs)** to your Docker daemon to verify registry server certificates, and **client certificates**, to authenticate to registries. + +Docker Desktop supports all trusted Certificate Authorities (CAs) (root or +intermediate). Docker recognizes certs stored under Trust Root +Certification Authorities or Intermediate Certification Authorities. + +Docker Desktop creates a certificate bundle of all user-trusted CAs based on +the Windows certificate store, and appends it to Moby trusted certificates. Therefore, if an enterprise SSL certificate is trusted by the user on the host, it is trusted by Docker Desktop. + +To learn more about how to install a CA root certificate for the registry, see +[Verify repository client with certificates](../../engine/security/certificates.md) +in the Docker Engine topics. + +### How do I add client certificates? + +You can add your client certificates +in `~/.docker/certs.d//client.cert` and +`~/.docker/certs.d//client.key`. You do not need to push your certificates with `git` commands. + +When the Docker Desktop application starts, it copies the +`~/.docker/certs.d` folder on your Windows system to the `/etc/docker/certs.d` +directory on Moby (the Docker Desktop virtual machine running on Hyper-V). + +You need to restart Docker Desktop after making any changes to the keychain +or to the `~/.docker/certs.d` directory in order for the changes to take effect. + +The registry cannot be listed as an _insecure registry_ (see +[Docker Daemon](../settings/windows-settings.md#docker-engine)). Docker Desktop ignores +certificates listed under insecure registries, and does not send client +certificates. Commands like `docker run` that attempt to pull from the registry +produce error messages on the command line, as well as on the registry. + +To learn more about how to set the client TLS certificate for verification, see +[Verify repository client with certificates](../../engine/security/certificates.md) +in the Docker Engine topics. + +## How do I switch between Windows and Linux containers + +From the Docker Desktop menu, you can toggle which daemon (Linux or Windows) +the Docker CLI talks to. Select **Switch to Windows containers** to use Windows +containers, or select **Switch to Linux containers** to use Linux containers +(the default). + +For more information on Windows containers, refer to the following documentation: + +- Microsoft documentation on [Windows containers](https://docs.microsoft.com/en-us/virtualization/windowscontainers/about/index). + +- [Build and Run Your First Windows Server Container (Blog Post)](https://blog.docker.com/2016/09/build-your-first-docker-windows-server-container/) + gives a quick tour of how to build and run native Docker Windows containers on Windows 10 and Windows Server 2016 evaluation releases. + +- [Getting Started with Windows Containers (Lab)](https://github.com/docker/labs/blob/master/windows/windows-containers/README.md) + shows you how to use the [MusicStore](https://github.com/aspnet/MusicStore/blob/dev/README.md) + application with Windows containers. The MusicStore is a standard .NET application and, + [forked here to use containers](https://github.com/friism/MusicStore), is a good example of a multi-container application. + +- To understand how to connect to Windows containers from the local host, see + [I want to connect to a container from Windows](../networking.md#i-want-to-connect-to-a-container-from-the-host) + +> Settings dialog changes with Windows containers +> +> When you switch to Windows containers, the Settings dialog only shows those tabs that are active and apply to your Windows containers: +> + * [General](../settings/windows-settings.md#general) + * [Proxies](../settings/windows-settings.md#proxies) + * [Daemon](../settings/windows-settings.md#docker-engine) + +If you set proxies or daemon configuration in Windows containers mode, these +apply only on Windows containers. If you switch back to Linux containers, +proxies and daemon configurations return to what you had set for Linux +containers. Your Windows container settings are retained and become available +again when you switch back. diff --git a/desktop/get-started.md b/desktop/get-started.md new file mode 100644 index 000000000000..6743868e1a24 --- /dev/null +++ b/desktop/get-started.md @@ -0,0 +1,134 @@ +--- +description: Docker Dashboard +keywords: Docker Dashboard, manage, containers, gui, dashboard, images, user manual +title: Sign in and get started +redirect_from: +- /desktop/dashboard/ +- /docker-for-windows/ +- /docker-for-windows/index/ +- /docker-for-windows/started/ +- /engine/installation/windows/ +- /installation/windows/ +- /win/ +- /windows/ +- /windows/started/ +- /winkit/ +- /winkit/getting-started/ +- /desktop/linux/index/ +- /desktop/windows/index/ +- /docker-for-mac/ +- /docker-for-mac/index/ +- /docker-for-mac/mutagen/ +- /docker-for-mac/mutagen-caching/ +- /docker-for-mac/osx/ +- /docker-for-mac/started/ +- /engine/installation/mac/ +- /installation/mac/ +- /mac/ +- /mac/started/ +- /mackit/ +- /mackit/getting-started/ +- /docker-for-mac/osxfs/ +- /docker-for-mac/osxfs-caching/ +- /desktop/mac/index/ +--- + +## Sign in to Docker Desktop + +After you’ve successfully installed and started Docker Desktop, we recommend that you authenticate using the **Sign in/Create ID** option in the top-right corner of Docker Desktop. + +Once logged in, you can access your Docker Hub repositories directly from Docker Desktop. + +Authenticated users get a higher pull rate limit compared to anonymous users. For example, if you are authenticated, you get 200 pulls per 6 hour period, compared to 100 pulls per 6 hour period per IP address for anonymous users. For more information, see [Download rate limit](https://docs.docker.com/docker-hub/download-rate-limit/). + +In large enterprises where admin access is restricted, administrators can create a registry.json file and deploy it to the developers’ machines using a device management software as part of the Docker Desktop installation process. Enforcing developers to authenticate through Docker Desktop also allows administrators to set up guardrails using features such as [Image Access Management](https://docs.docker.com/docker-hub/image-access-management/) which allows team members to only have access to Trusted Content on Docker Hub, and pull only from the specified categories of images. For more information, see Configure registry.json to enforce sign in https://docs.docker.com/docker-hub/configure-sign-in/. + +### Two-factor authentication + +Docker Desktop enables you to sign into Docker Hub using two-factor authentication. Two-factor authentication provides an extra layer of security when accessing your Docker Hub account. + +You must enable two-factor authentication in Docker Hub before signing into your Docker Hub account through Docker Desktop. For instructions, see [Enable two-factor authentication for Docker Hub](/docker-hub/2fa/). + +After you have enabled two-factor authentication: + +1. Go to the Docker Desktop menu and then select **Sign in / Create Docker ID**. + +2. Enter your Docker ID and password and click **Sign in**. + +3. After you have successfully signed in, Docker Desktop prompts you to enter the authentication code. Enter the six-digit code from your phone and then click **Verify**. + +### Credentials management for Linux users + +Docker Desktop relies on [`pass`](https://www.passwordstore.org/){: target="_blank" rel="noopener" class="_"} to store credentials in gpg2-encrypted files. +Before signing in to Docker Hub from the Docker Dashboard or the Docker menu, you must initialize `pass`. +Docker Desktop displays a warning if you've not initialized `pass`. + +You can intialize pass by using a gpg key. To generate a gpg key, run: + +``` console +$ gpg --generate-key +... +GnuPG needs to construct a user ID to identify your key. + +Real name: Molly +Email address: molly@example.com +You selected this USER-ID: + "Molly " + +Change (N)ame, (E)mail, or (O)kay/(Q)uit? O +... +pub rsa3072 2022-03-31 [SC] [expires: 2024-03-30] + 7865BA9185AFA2C26C5B505669FC4F36530097C2 +uid Molly +sub rsa3072 2022-03-31 [E] [expires: 2024-03-30] +``` + +To initialize `pass`, run: + +```console +molly@ubuntu:~$ pass init 7865BA9185AFA2C26C5B505669FC4F36530097C2 +mkdir: created directory '/home/molly/.password-store/' +Password store initialized for 7865BA9185AFA2C26C5B505669FC4F36530097C2 +``` + +Once `pass` is initialized, we can sign in on the Docker Dashboard and pull our private images. +When credentials are used by the Docker CLI or Docker Desktop, a user prompt may pop up for the password you set during the gpg key generation. + +```console +$ docker pull molly/privateimage +Using default tag: latest +latest: Pulling from molly/privateimage +3b9cc81c3203: Pull complete +Digest: sha256:3c6b73ce467f04d4897d7a7439782721fd28ec9bf62ea2ad9e81a5fb7fb3ff96 +Status: Downloaded newer image for molly/privateimage:latest +docker.io/molly/privateimage:latest +``` + +## Overview of Docker Dashboard + +When you open Docker Desktop, the Docker Dashboard display. It provides a simple interface that enables you to manage your containers, applications, and images directly from your machine without having to use the CLI to perform core actions. + +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](containers.md). + +The **Images** view displays a list of your Docker images, and allows you to run an image as a container, pull the latest version of an image from Docker Hub, and inspect images. It also displays a summary of the vulnerability scanning report using Snyk. In addition, the Images view contains clean up options to remove unwanted images from the disk to reclaim space. If you are logged in, you can also see the images you and your organization have shared on Docker Hub. For more information, see [Explore your images](images.md) + +The **Volumes** view displays a list of volumes and allows you to easily create and delete volumes and see which ones are being used. For more information, see [Explore volumes](volumes.md). + +In addition, the Docker Dashboard allows you to: + +- Easily navigate to the **Preferences** (**Settings** in Windows) menu to configure Docker Desktop preferences. Select the **Preferences** or **Settings** icon in Dashboard header. +- Access the **Troubleshoot** menu to debug and perform restart operations. Select the **Troubleshoot** icon in Dashboard header. + +## Pause or resume Docker Desktop + +Starting with the Docker Desktop 4.2 release, you can pause your Docker Desktop session when you are not actively using it and save CPU resources on your machine. When you pause Docker Desktop, the Linux VM running Docker Engine is paused, the current state of all your containers are saved in memory, and all processes are frozen. This reduces the CPU usage and helps you retain a longer battery life on your laptop. You can resume Docker Desktop when you want by clicking the Resume option. + +From the Docker menu, select![whale menu](../images/whale-x.png){: .inline} and then **Pause** to pause Docker Desktop. + +Docker Desktop displays the paused status on the Docker menu and on the **Containers**, **Images**, **Volumes**, and **Dev Environment** screens in Docker Dashboard. You can still access the **Preferences** (or **Settings** if you are a Windows user) and the **Troubleshoot** menu from the Dashboard when you've paused Docker Desktop. + +Select ![whale menu](images/whale-x.png){: .inline} then **Resume** to resume Docker Desktop. + +> **Note** +> +> When Docker Desktop is paused, running any commands in the Docker CLI will automatically resume Docker Desktop. \ No newline at end of file diff --git a/desktop/use-desktop/container.md b/desktop/use-desktop/container.md new file mode 100644 index 000000000000..e715a4d09666 --- /dev/null +++ b/desktop/use-desktop/container.md @@ -0,0 +1,98 @@ +--- +description: Docker Dashboard +keywords: Docker Dashboard, manage, containers, gui, dashboard, images, user manual +title: Explore Containers +--- + +The **Containers** tab lists all your running containers and applications. You must have running or stopped containers and applications to see them listed. + +The following sections guide you through the process of creating a sample Redis container and a sample application to demonstrate the core functionalities in Docker Dashboard. + +### Start a Redis container + +To start a Redis container, open your preferred CLI and run the following command: + +`docker run -dt redis` + +This creates a new Redis container. From the Docker menu, select **Dashboard** to see the new Redis container. + +### Start a sample application + +Let's start a sample application. Download the [Example voting app](https://github.com/dockersamples/example-voting-app) from the Docker samples page. The example voting app is a distributed application that runs across multiple Docker containers. The app contains: + +- A front-end web app in [Python](https://github.com/dockersamples/example-voting-app/blob/master/vote) or [ASP.NET Core](https://github.com/dockersamples/example-voting-app/blob/master/vote/dotnet) which lets you vote between two options +- A [Redis](https://hub.docker.com/_/redis/) or [NATS](https://hub.docker.com/_/nats/) queue which collects new votes +- A [.NET Core](https://github.com/dockersamples/example-voting-app/blob/master/worker/src/Worker), [Java](https://github.com/dockersamples/example-voting-app/blob/master/worker/src/main) or [.NET Core 2.1](https://github.com/dockersamples/example-voting-app/blob/master/worker/dotnet) worker which consumes votes and stores them +- A [Postgres](https://hub.docker.com/_/postgres/) or [TiDB](https://hub.docker.com/r/dockersamples/tidb/tags/) database backed by a Docker volume +- A [Node.js](https://github.com/dockersamples/example-voting-app/blob/master/result) or [ASP.NET Core SignalR](https://github.com/dockersamples/example-voting-app/blob/master/result/dotnet) web app which shows the results of the voting in real time + +To start the application, navigate to the directory containing the example voting application in the CLI and run `docker-compose up --build`. + +```console +$ docker-compose up --build +Creating network "example-voting-app-master_front-tier" with the default driver +Creating network "example-voting-app-master_back-tier" with the default driver +Creating volume "example-voting-app-master_db-data" with default driver +Building vote +Step 1/7 : FROM python:2.7-alpine +2.7-alpine: Pulling from library/python +Digest: sha256:d2cc8451e799d4a75819661329ea6e0d3e13b3dadd56420e25fcb8601ff6ba49 +Status: Downloaded newer image for python:2.7-alpine + ---> 1bf48bb21060 +Step 2/7 : WORKDIR /app + +... +Successfully built 69da1319c6ce +Successfully tagged example-voting-app-master_worker:latest +Creating example-voting-app-master_vote_1 ... done +Creating example-voting-app-master_result_1 ... done +Creating db ... done +Creating redis ... done +Creating example-voting-app-master_worker_1 ... done +Attaching to db, redis, example-voting-app-master_result_1, example-voting-app-master_vote_1, example-voting-app-master_worker_1 +... +``` + +When the application starts successfully, from the Docker menu, select **Dashboard** to see the Example voting application. Expand the application to see the containers running inside the application. + +Now that you can see the list of running containers and applications on the Dashboard, let us explore some of the actions you can perform: + +- Click **Port** to open the port exposed by the container in a browser. +- Click **CLI** to open a terminal and run commands on the container. If you have installed iTerm2 on your Mac, the CLI option opens an iTerm2 terminal. Otherwise, it opens the Terminal app on Mac, or a Command Prompt on Windows. +- Click **Stop**, **Start**, **Restart**, or **Delete** to perform lifecycle operations on the container. + +Use the **Search** option to search for a specific object. You can also sort your containers and applications using various options. Click the **Sort by** drop-down to see a list of available options. + +### Interact with containers and applications + +From the Docker Dashboard, select the example voting application we started earlier. + +The **Containers** view lists all the containers running on the application and contains a detailed logs view. It also allows you to start, stop, or delete the application. Use the **Search** option at the bottom of the logs view to search application logs for specific events, or select the **Copy** icon to copy the logs to your clipboard. + +From the **Containers** view you can also perform the following actions on multiple containers at once: +- Pause +- Resume +- Stop +- Start +- Delete + +Click **Open in Visual Studio Code** to open the application in VS Code. Hover over the list of containers to see some of the core actions you can perform. + +### Container view + +Click on a specific container for detailed information about the container. The **container view** displays **Logs**, **Inspect**, and **Stats** tabs and provides quick action buttons to perform various actions. + +- Select **Logs** to see logs from the container. You can also: + - Use `Cmd + f`/`Ctrl + f` to open the search bar and find specific entries. Search matches are highlighted in yellow. + - Press `Enter` or `Shit + Enter` to jump to the next or previous search match respectively. + - Use the **Copy** icon in the top right-hand corner to copy all the logs to your clipboard. + - Automatically copy any logs content by highlighting a few lines or a section of the logs. + - Use the **Clear terminal** icon in the top right-hand corner to clear the logs terminal. + - Select and view external links that may be in your logs. + + +- Select **Inspect** to view low-level information about the container. You can see the local path, version number of the image, SHA-256, port mapping, and other details. + +- Select **Stats** to view information about the container resource utilization. You can see the amount of CPU, disk I/O, memory, and network I/O used by the container. + +You can also use the quick action buttons on the top bar to perform common actions such as opening a CLI to run commands in a container, and perform lifecycle operations such as stop, start, restart, or delete your container. \ No newline at end of file diff --git a/desktop/use-desktop/images.md b/desktop/use-desktop/images.md new file mode 100644 index 000000000000..8d797aedac92 --- /dev/null +++ b/desktop/use-desktop/images.md @@ -0,0 +1,110 @@ +--- +description: Docker Dashboard +keywords: Docker Dashboard, manage, containers, gui, dashboard, images, user manual +title: Explore Images +--- + +The **Images** view is a simple interface that lets you manage Docker images without having to use the CLI. By default, it displays a list of all Docker images on your local disk. To view images in remote repositories, click **Sign in** and connect to Docker Hub. This allows you to collaborate with your team and manage your images directly through Docker Desktop. + +The Images view allows you to perform core operations such as running an image as a container, pulling the latest version of an image from Docker Hub, pushing the image to Docker Hub, and inspecting images. + +In addition, the Images view displays metadata about the image such as the tag, image ID, date when the image was created, and the size of the image. It also displays **In Use** tags next to images used by running and stopped containers. This allows you to review the list of images and use the **Clean up images** option to remove any unwanted images from the disk to reclaim space. + +The Images view also allows you to search images on your local disk and sort them using various options. + +Let's explore the various options in the **Images** view. + +If you don’t have any images on your disk, run the command `docker pull redis` in a terminal to pull the latest Redis image. This command pulls the latest Redis image from Docker Hub. + +Select **Dashboard** > **Images** to see the Redis image. + +![Redis image](images/redis-image.png){:width="700px"} + +### Run an image as a container + +Now that you have a Redis image on your disk, let’s run this image as a container: + +1. From Docker Dashboard, select **Images**. A list of images on your local disk displays. +2. Select the Redis image from the list and click **Run**. +3. Optional step: When prompted, click the **Optional settings** drop-down to specify a name, port, volumes, environment variables and click **Run**. + + To use the defaults, click **Run** without specifying any optional settings. This creates a new container from the Redis image and opens it on the **Containers** view. + +### Pull the latest image from Docker Hub + +To pull the latest image from Docker Hub: + +1. From the Docker menu, select **Dashboard** > **Images**. This displays a list of images on your local disk. +2. Select the image from the list and click the more options button. +3. Click **Pull**. This pulls the latest version of the image from Docker Hub. + +> **Note** +> +> The repository must exist on Docker Hub in order to pull the latest version of an image. You must be logged in to pull private images. +### Push an image to Docker Hub + +To push an image to Docker Hub: + +1. From the Docker menu, select **Dashboard** > **Images**. This displays a list of images on your local disk. +2. Select the image from the list and click the more options button. +3. Click **Push to Hub.** + +> **Note** +> +> You can only push an image to Docker Hub if the image belongs to your Docker ID or your organization. That is, the image must contain the correct username/organization in its tag to be able to push it to Docker Hub. +### Inspect an image + +Inspecting an image displays detailed information about the image such as the image history, image ID, the date the image was created, size of the image, etc. To inspect an image: + +1. From the Docker menu, select **Dashboard** > **Images**. This displays a list of images on your local disk. +2. Select the image from the list and click the more options button. +3. Click **Inspect**. +4. The image inspect view also provides options to pull the latest image, push image to Hub, remove the image, or run the image as a container. + +### Remove an image + +The **Images** view allows you to remove unwanted images from the disk. The Images on disk status bar displays the number of images and the total disk space used by the images. + +You can remove individual images or use the **Clean up** option to delete unused and dangling images. + +To remove individual images: + +1. From the Docker menu, select **Dashboard** > **Images**. This displays a list of images on your local disk. +2. Select the image from the list and click the more options button. +3. Click **Remove**. This removes the image from your disk. + +> **Note** +> +> To remove an image used by a running or a stopped container, you must first remove the associated container. +**To remove unused and dangling images:** + +An **unused** image is an image which is not used by any running or stopped containers. An image becomes **dangling** when you build a new version of the image with the same tag. + +**To remove an unused or a dangling image:** + +1. From the Docker menu, select **Dashboard** > **Images**. This displays a list of images on your disk. +2. Select the **Clean up** option from the **Images on disk** status bar. +3. Use the **Unused** and **Dangling** check boxes to select the type of images you would like to remove. + + The **Clean up** images status bar displays the total space you can reclaim by removing the selected images. +4. Click **Remove** to confirm. + +### Interact with remote repositories + +The Images view also allows you to manage and interact with images in remote repositories and lets you switch between organizations. Select an organization from the drop-down to view a list of repositories in your organization. + +> **Note** +> +> If you have a paid Docker subscription and enabled [Vulnerability Scanning](../../docker-hub/vulnerability-scanning.md) in Docker Hub, the scan results will appear on the Remote repositories tab. +The **Pull** option allows you to pull the latest version of the image from Docker Hub. The **View in Hub** option opens the Docker Hub page and displays detailed information about the image, such as the OS architecture, size of the image, the date when the image was pushed, and a list of the image layers. + +To interact with remote repositories: + +1. Click the **Remote repositories** tab. +2. Select an organization from the drop-down list. This displays a list of repositories in your organization. +3. Click on an image from the list and then select **Pull** to pull the latest image from the remote repository. +4. To view a detailed information about the image in Docker Hub, select the image and then click **View in Hub**. + + The **View in Hub** option opens the Docker Hub page and displays detailed information about the image, such as the OS architecture, size of the image, the date when the image was pushed, and a list of the image layers. + + If you have a paid Docker subscription and have enabled [Vulnerability Scanning](../../docker-hub/vulnerability-scanning.md) the Docker Hub page also displays a summary of the vulnerability scan report and provides detailed information about the vulnerabilities identified. \ No newline at end of file diff --git a/desktop/use-desktop/volumes.md b/desktop/use-desktop/volumes.md new file mode 100644 index 000000000000..d12703e14b40 --- /dev/null +++ b/desktop/use-desktop/volumes.md @@ -0,0 +1,32 @@ +--- +description: Docker Dashboard +keywords: Docker Dashboard, manage, containers, gui, dashboard, images, user manual +title: Explore Volumes +--- +## Explore volumes + +You can use [volumes](../../storage/volumes.md) to store files and share them among containers. Volumes are created and are directly managed by Docker. They are also the preferred mechanism to persist data in Docker containers and services. + +> **Volume Management is now available for all subscriptions** +> +> Starting with Docker Desktop 4.1.0 release, Volume management is available for users on any subscription, including Docker Personal. Update Docker Desktop to 4.1.0 to start managing your volumes for free. +{: .important} +The **Volumes** view in Docker Dashboard enables you to easily create and delete volumes and see which ones are being used. You can also see which container is using a specific volume and explore the files and folders in your volumes. + +### Manage volumes + +By default, the **Volumes** view displays a list of all the volumes. Volumes that are currently used by a container display the **In Use** badge. + +Use the **Search** field to search for any specific volumes. You can also sort volumes by the name, the date created, and the size of the volume. + +To explore the details of a specific volume, select a volume from the list. This opens the detailed view. + +The **In Use** tab displays the name of the container using the volume, the image name, the port number used by the container, and the target. A target is a path inside a container that gives access to the files in the volume. + +The **Data** tab displays the files and folders in the volume and their file size. To save a file or a folder, hover over the file or folder and click on the more options menu. Select **Save As** and then specify a location to download the file. + +To delete a file or a folder from the volume, select **Remove** from the more options menu. + +### Remove a volume + +Removing a volume deletes the volume and all its data. To remove a volume, hover over the volume and then click the **Delete** button. Alternatively, select the volume from the list and then click the **Delete** button. \ No newline at end of file From ab9abda99ae42c199a3cdba7ab085d77deaa9990 Mon Sep 17 00:00:00 2001 From: Allie Sadler <102604716+aevesdocker@users.noreply.github.com> Date: Mon, 18 Jul 2022 14:57:04 +0100 Subject: [PATCH 2/6] fix broken links --- _data/toc.yaml | 2 +- desktop/faqs/macfaqs.md | 2 +- desktop/faqs/windowsfaqs.md | 8 ++++---- desktop/get-started.md | 6 +++--- desktop/previous-versions/3.x-mac.md | 4 ++-- desktop/use-desktop/images.md | 2 -- language/python/build-images.md | 2 +- 7 files changed, 12 insertions(+), 14 deletions(-) diff --git a/_data/toc.yaml b/_data/toc.yaml index 013e435001bf..6fb7670e1cfd 100644 --- a/_data/toc.yaml +++ b/_data/toc.yaml @@ -1159,7 +1159,7 @@ manuals: title: Sign in and get started - sectiontitle: Explore Docker Desktop section: - - path: /desktop/use-desktop/containers/ + - path: /desktop/use-desktop/container/ title: Explore Containers - path: /desktop/use-desktop/images/ title: Explore Images diff --git a/desktop/faqs/macfaqs.md b/desktop/faqs/macfaqs.md index 5472cfe9f8ca..b981cffba57d 100644 --- a/desktop/faqs/macfaqs.md +++ b/desktop/faqs/macfaqs.md @@ -171,7 +171,7 @@ Desktop `xhyve` virtual machine). > effect. > > * The registry cannot be listed as an _insecure registry_ (see [Docker -> Engine](../settings/mac-settings#docker-engine). Docker Desktop ignores certificates listed +> Engine](../settings/mac#docker-engine). Docker Desktop ignores certificates listed > under insecure registries, and does not send client certificates. Commands > like `docker run` that attempt to pull from the registry produce error > messages on the command line, as well as on the registry. diff --git a/desktop/faqs/windowsfaqs.md b/desktop/faqs/windowsfaqs.md index 7590733d0651..f9f070a3cfbe 100644 --- a/desktop/faqs/windowsfaqs.md +++ b/desktop/faqs/windowsfaqs.md @@ -91,7 +91,7 @@ You need to restart Docker Desktop after making any changes to the keychain or to the `~/.docker/certs.d` directory in order for the changes to take effect. The registry cannot be listed as an _insecure registry_ (see -[Docker Daemon](../settings/windows-settings.md#docker-engine)). Docker Desktop ignores +[Docker Daemon](../settings/windows.md#docker-engine)). Docker Desktop ignores certificates listed under insecure registries, and does not send client certificates. Commands like `docker run` that attempt to pull from the registry produce error messages on the command line, as well as on the registry. @@ -126,9 +126,9 @@ For more information on Windows containers, refer to the following documentation > > When you switch to Windows containers, the Settings dialog only shows those tabs that are active and apply to your Windows containers: > - * [General](../settings/windows-settings.md#general) - * [Proxies](../settings/windows-settings.md#proxies) - * [Daemon](../settings/windows-settings.md#docker-engine) + * [General](../settings/windows.md#general) + * [Proxies](../settings/windows.md#proxies) + * [Daemon](../settings/windows.md#docker-engine) If you set proxies or daemon configuration in Windows containers mode, these apply only on Windows containers. If you switch back to Linux containers, diff --git a/desktop/get-started.md b/desktop/get-started.md index 6743868e1a24..0ab33f085cb8 100644 --- a/desktop/get-started.md +++ b/desktop/get-started.md @@ -108,11 +108,11 @@ docker.io/molly/privateimage:latest When you open Docker Desktop, the Docker Dashboard display. It provides a simple interface that enables you to manage your containers, applications, and images directly from your machine without having to use the CLI to perform core actions. -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](containers.md). +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](use-desktop/container.md). -The **Images** view displays a list of your Docker images, and allows you to run an image as a container, pull the latest version of an image from Docker Hub, and inspect images. It also displays a summary of the vulnerability scanning report using Snyk. In addition, the Images view contains clean up options to remove unwanted images from the disk to reclaim space. If you are logged in, you can also see the images you and your organization have shared on Docker Hub. For more information, see [Explore your images](images.md) +The **Images** view displays a list of your Docker images, and allows you to run an image as a container, pull the latest version of an image from Docker Hub, and inspect images. It also displays a summary of the vulnerability scanning report using Snyk. In addition, the Images view contains clean up options to remove unwanted images from the disk to reclaim space. If you are logged in, you can also see the images you and your organization have shared on Docker Hub. For more information, see [Explore your images](use-desktop/images.md) -The **Volumes** view displays a list of volumes and allows you to easily create and delete volumes and see which ones are being used. For more information, see [Explore volumes](volumes.md). +The **Volumes** view displays a list of volumes and allows you to easily create and delete volumes and see which ones are being used. For more information, see [Explore volumes](use-desktop/volumes.md). In addition, the Docker Dashboard allows you to: diff --git a/desktop/previous-versions/3.x-mac.md b/desktop/previous-versions/3.x-mac.md index 71ee099e7fc6..74c1f3b9c3ec 100644 --- a/desktop/previous-versions/3.x-mac.md +++ b/desktop/previous-versions/3.x-mac.md @@ -36,7 +36,7 @@ This page contains information about the new features, improvements, known issue ### New - **Dev Environments**: You can now create a Dev Environment from your local Git repository. For more information, see [Create a Dev Environment from a local folder](../dev-environments/create-dev-env.md#create-a-dev-environment-from-a-local-folder). -- **Volume Management**: You can now sort volumes by the name, the date created, and the size of the volume. You can also search for specific volumes using the **Search** field. For more information, see [Explore volumes](../dashboard.md#explore-volumes). +- **Volume Management**: You can now sort volumes by the name, the date created, and the size of the volume. You can also search for specific volumes using the **Search** field. For more information, see [Explore volumes](../use-desktop/volumes.md). ### Upgrades @@ -167,7 +167,7 @@ This page contains information about the new features, improvements, known issue ### New -**Volume Management**: Docker Desktop users can now create and delete volumes using the Docker Dashboard and also see which volumes are being used. For more information, see [Explore volumes](../dashboard.md#explore-volumes). +**Volume Management**: Docker Desktop users can now create and delete volumes using the Docker Dashboard and also see which volumes are being used. For more information, see [Explore volumes](../use-desktop/volumes.md). **Compose V2 beta**: Docker Desktop now includes the beta version of Compose V2, which supports the `docker compose` command as part of the Docker CLI. While `docker-compose` is still supported and maintained, Compose V2 implementation relies directly on the compose-go bindings which are maintained as part of the specification. The compose command in the Docker CLI supports most of the `docker-compose` commands and flags. It is expected to be a drop-in replacement for `docker-compose`. There are a few remaining flags that have yet to be implemented, see the [docker-compose compatibility list](../../compose/cli-command-compatibility.md) for more information about the flags that are supported in the new compose command. If you run into any problems with Compose V2, you can easily switch back to Compose v1 by either by making changes in Docker Desktop **Experimental** Settings, or by running the command `docker-compose disable-v2`. Let us know your feedback on the new ‘compose’ command by creating an issue in the [Compose-CLI](https://github.com/docker/compose-cli/issues) GitHub repository. diff --git a/desktop/use-desktop/images.md b/desktop/use-desktop/images.md index 8d797aedac92..44bcce79cad7 100644 --- a/desktop/use-desktop/images.md +++ b/desktop/use-desktop/images.md @@ -18,8 +18,6 @@ If you don’t have any images on your disk, run the command `docker pull redis` Select **Dashboard** > **Images** to see the Redis image. -![Redis image](images/redis-image.png){:width="700px"} - ### Run an image as a container Now that you have a Redis image on your disk, let’s run this image as a container: diff --git a/language/python/build-images.md b/language/python/build-images.md index 5638f400e1fb..a6780337bda6 100644 --- a/language/python/build-images.md +++ b/language/python/build-images.md @@ -173,7 +173,7 @@ $ docker build --tag python-docker . ## View local images -To see a list of images we have on our local machine, we have two options. One is to use the CLI and the other is to use [Docker Desktop](../../desktop/dashboard.md#explore-your-images). As we are currently working in the terminal let’s take a look at listing images using the CLI. +To see a list of images we have on our local machine, we have two options. One is to use the CLI and the other is to use [Docker Desktop](../../desktop/use-desktop/images.md). As we are currently working in the terminal let’s take a look at listing images using the CLI. To list images, simply run the `docker images` command. From 0395818558e3c1c7abce6d53ca74df8df86d18be Mon Sep 17 00:00:00 2001 From: Allie Sadler <102604716+aevesdocker@users.noreply.github.com> Date: Mon, 18 Jul 2022 15:06:52 +0100 Subject: [PATCH 3/6] fix broken links --- desktop/faqs/macfaqs.md | 2 +- desktop/previous-versions/3.x-windows.md | 4 ++-- language/java/build-images.md | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/desktop/faqs/macfaqs.md b/desktop/faqs/macfaqs.md index b981cffba57d..917f456618d7 100644 --- a/desktop/faqs/macfaqs.md +++ b/desktop/faqs/macfaqs.md @@ -171,7 +171,7 @@ Desktop `xhyve` virtual machine). > effect. > > * The registry cannot be listed as an _insecure registry_ (see [Docker -> Engine](../settings/mac#docker-engine). Docker Desktop ignores certificates listed +> Engine](../settings/mac.md#docker-engine). Docker Desktop ignores certificates listed > under insecure registries, and does not send client certificates. Commands > like `docker run` that attempt to pull from the registry produce error > messages on the command line, as well as on the registry. diff --git a/desktop/previous-versions/3.x-windows.md b/desktop/previous-versions/3.x-windows.md index 4d5a322e5fd2..139fc425bf94 100644 --- a/desktop/previous-versions/3.x-windows.md +++ b/desktop/previous-versions/3.x-windows.md @@ -35,7 +35,7 @@ This page contains information about the new features, improvements, known issue ### New - **Dev Environments**: You can now create a Dev Environment from your local Git repository. For more information, see [Create a Dev Environment from a local folder](../dev-environments/create-dev-env.md#create-a-dev-environment-from-a-local-folder). -- **Volume Management**: You can now sort volumes by the name, the date created, and the size of the volume. You can also search for specific volumes using the **Search** field. For more information, see [Explore volumes](../dashboard.md#explore-volumes). +- **Volume Management**: You can now sort volumes by the name, the date created, and the size of the volume. You can also search for specific volumes using the **Search** field. For more information, see [Explore volumes](../use-desktop/volumes.md). ### Upgrades @@ -169,7 +169,7 @@ This page contains information about the new features, improvements, known issue ### New -**Volume Management**: Docker Desktop users can now create and delete volumes using the Docker Dashboard and also see which volumes are being used. For more information, see [Explore volumes](../dashboard.md#explore-volumes). +**Volume Management**: Docker Desktop users can now create and delete volumes using the Docker Dashboard and also see which volumes are being used. For more information, see [Explore volumes](../use-desktop/volumes.md). **Compose V2 beta**: Docker Desktop now includes the beta version of Compose V2, which supports the `docker compose` command as part of the Docker CLI. While `docker-compose` is still supported and maintained, Compose V2 implementation relies directly on the compose-go bindings which are maintained as part of the specification. The compose command in the Docker CLI supports most of the `docker-compose` commands and flags. It is expected to be a drop-in replacement for `docker-compose`. There are a few remaining flags that have yet to be implemented, see the [docker-compose compatibility list](../../compose/cli-command-compatibility.md) for more information about the flags that are supported in the new compose command. If you run into any problems with Compose V2, you can easily switch back to Compose v1 by either by making changes in Docker Desktop **Experimental** Settings, or by running the command `docker-compose disable-v2`. Let us know your feedback on the new ‘compose’ command by creating an issue in the [Compose-CLI](https://github.com/docker/compose-cli/issues) GitHub repository. diff --git a/language/java/build-images.md b/language/java/build-images.md index 2596db92e1ba..2afa8f237d48 100644 --- a/language/java/build-images.md +++ b/language/java/build-images.md @@ -185,7 +185,7 @@ Successfully tagged java-docker:latest ## View local images -To see a list of images we have on our local machine, we have two options. One is to use the CLI and the other is to use [Docker Desktop](../../desktop/dashboard.md#explore-your-images). As we are currently working in the terminal let’s take a look at listing images using the CLI. +To see a list of images we have on our local machine, we have two options. One is to use the CLI and the other is to use [Docker Desktop](../../use-desktop/images.md). As we are currently working in the terminal let’s take a look at listing images using the CLI. To list images, simply run the `docker images` command. From aa66ce2aa33c29d3332de096f2f7101c64550506 Mon Sep 17 00:00:00 2001 From: Allie Sadler <102604716+aevesdocker@users.noreply.github.com> Date: Mon, 18 Jul 2022 15:14:02 +0100 Subject: [PATCH 4/6] fix broken links --- desktop/faqs/macfaqs.md | 3 +-- language/java/build-images.md | 2 +- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/desktop/faqs/macfaqs.md b/desktop/faqs/macfaqs.md index 917f456618d7..47f24074a065 100644 --- a/desktop/faqs/macfaqs.md +++ b/desktop/faqs/macfaqs.md @@ -170,8 +170,7 @@ Desktop `xhyve` virtual machine). > or to the `~/.docker/certs.d` directory in order for the changes to take > effect. > -> * The registry cannot be listed as an _insecure registry_ (see [Docker -> Engine](../settings/mac.md#docker-engine). Docker Desktop ignores certificates listed +> * The registry cannot be listed as an _insecure registry_. Docker Desktop ignores certificates listed > under insecure registries, and does not send client certificates. Commands > like `docker run` that attempt to pull from the registry produce error > messages on the command line, as well as on the registry. diff --git a/language/java/build-images.md b/language/java/build-images.md index 2afa8f237d48..2e8a9d50d7c4 100644 --- a/language/java/build-images.md +++ b/language/java/build-images.md @@ -185,7 +185,7 @@ Successfully tagged java-docker:latest ## View local images -To see a list of images we have on our local machine, we have two options. One is to use the CLI and the other is to use [Docker Desktop](../../use-desktop/images.md). As we are currently working in the terminal let’s take a look at listing images using the CLI. +To see a list of images we have on our local machine, we have two options. One is to use the CLI and the other is to use [Docker Desktop](../../desktop/use-desktop/images.md). As we are currently working in the terminal let’s take a look at listing images using the CLI. To list images, simply run the `docker images` command. From 37d6fd4710e8241218d5bb5289dfb8390f03d1c9 Mon Sep 17 00:00:00 2001 From: Allie Sadler <102604716+aevesdocker@users.noreply.github.com> Date: Tue, 19 Jul 2022 10:34:07 +0100 Subject: [PATCH 5/6] updates --- _data/toc.yaml | 4 +- desktop/get-started.md | 38 ++++++--------- desktop/images/dashboard.PNG | Bin 0 -> 30890 bytes .../images/docker-tutorial-linux.png | Bin desktop/index.md | 46 +++++++++++++----- desktop/install/linux-install.md | 12 +---- desktop/install/mac-install.md | 9 ---- desktop/install/windows-install.md | 10 ---- desktop/use-desktop/volumes.md | 30 +++++++----- 9 files changed, 70 insertions(+), 79 deletions(-) create mode 100644 desktop/images/dashboard.PNG rename desktop/{install => }/images/docker-tutorial-linux.png (100%) diff --git a/_data/toc.yaml b/_data/toc.yaml index 6fb7670e1cfd..01d03bc30b2a 100644 --- a/_data/toc.yaml +++ b/_data/toc.yaml @@ -1156,7 +1156,7 @@ manuals: - path: /desktop/install/archlinux/ title: Install on Arch - path: /desktop/get-started/ - title: Sign in and get started + title: Quick Start Guide and sign in - sectiontitle: Explore Docker Desktop section: - path: /desktop/use-desktop/container/ @@ -1182,7 +1182,7 @@ manuals: - sectiontitle: Linux section: - path: /desktop/linux/troubleshoot/ - title: Logs and troubleshooting + title: Logs and troubleshooting - sectiontitle: Change settings section: - path: /desktop/settings/mac/ diff --git a/desktop/get-started.md b/desktop/get-started.md index 0ab33f085cb8..224a428ec2dc 100644 --- a/desktop/get-started.md +++ b/desktop/get-started.md @@ -3,7 +3,6 @@ description: Docker Dashboard keywords: Docker Dashboard, manage, containers, gui, dashboard, images, user manual title: Sign in and get started redirect_from: -- /desktop/dashboard/ - /docker-for-windows/ - /docker-for-windows/index/ - /docker-for-windows/started/ @@ -33,9 +32,19 @@ redirect_from: - /desktop/mac/index/ --- +## Quick Start Guide + + Once Docker Desktop is installed, the Quick Start Guide launches. It includes a simple exercise to build an example Docker image, run it as a container, push and save the image to Docker Hub. + + ![Docker Quick Start tutorial](images/docker-tutorial-linux.png) + +To run the Quick Start Guide on demand, select ![whale menu](images/whale-x.png){: .inline} and then choose **Quick Start Guide**. + +For a more detailed guide, see [Get started](../get-started/index.md) + ## Sign in to Docker Desktop -After you’ve successfully installed and started Docker Desktop, we recommend that you authenticate using the **Sign in/Create ID** option in the top-right corner of Docker Desktop. +We recommend that you authenticate using the **Sign in/Create ID** option in the top-right corner of Docker Desktop. Once logged in, you can access your Docker Hub repositories directly from Docker Desktop. @@ -45,11 +54,11 @@ In large enterprises where admin access is restricted, administrators can create ### Two-factor authentication -Docker Desktop enables you to sign into Docker Hub using two-factor authentication. Two-factor authentication provides an extra layer of security when accessing your Docker Hub account. +Docker Desktop enables you to sign in to Docker Hub using two-factor authentication. Two-factor authentication provides an extra layer of security when accessing your Docker Hub account. You must enable two-factor authentication in Docker Hub before signing into your Docker Hub account through Docker Desktop. For instructions, see [Enable two-factor authentication for Docker Hub](/docker-hub/2fa/). -After you have enabled two-factor authentication: +After two-factor authentication is enabled: 1. Go to the Docker Desktop menu and then select **Sign in / Create Docker ID**. @@ -91,7 +100,7 @@ mkdir: created directory '/home/molly/.password-store/' Password store initialized for 7865BA9185AFA2C26C5B505669FC4F36530097C2 ``` -Once `pass` is initialized, we can sign in on the Docker Dashboard and pull our private images. +Once `pass` is initialized, you can sign in on the Docker Dashboard and pull your private images. When credentials are used by the Docker CLI or Docker Desktop, a user prompt may pop up for the password you set during the gpg key generation. ```console @@ -104,26 +113,11 @@ Status: Downloaded newer image for molly/privateimage:latest docker.io/molly/privateimage:latest ``` -## Overview of Docker Dashboard - -When you open Docker Desktop, the Docker Dashboard display. It provides a simple interface that enables you to manage your containers, applications, and images directly from your machine without having to use the CLI to perform core actions. - -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](use-desktop/container.md). - -The **Images** view displays a list of your Docker images, and allows you to run an image as a container, pull the latest version of an image from Docker Hub, and inspect images. It also displays a summary of the vulnerability scanning report using Snyk. In addition, the Images view contains clean up options to remove unwanted images from the disk to reclaim space. If you are logged in, you can also see the images you and your organization have shared on Docker Hub. For more information, see [Explore your images](use-desktop/images.md) - -The **Volumes** view displays a list of volumes and allows you to easily create and delete volumes and see which ones are being used. For more information, see [Explore volumes](use-desktop/volumes.md). - -In addition, the Docker Dashboard allows you to: - -- Easily navigate to the **Preferences** (**Settings** in Windows) menu to configure Docker Desktop preferences. Select the **Preferences** or **Settings** icon in Dashboard header. -- Access the **Troubleshoot** menu to debug and perform restart operations. Select the **Troubleshoot** icon in Dashboard header. - ## Pause or resume Docker Desktop -Starting with the Docker Desktop 4.2 release, you can pause your Docker Desktop session when you are not actively using it and save CPU resources on your machine. When you pause Docker Desktop, the Linux VM running Docker Engine is paused, the current state of all your containers are saved in memory, and all processes are frozen. This reduces the CPU usage and helps you retain a longer battery life on your laptop. You can resume Docker Desktop when you want by clicking the Resume option. +You can pause your Docker Desktop session when you are not actively using it and save CPU resources on your machine. When you pause Docker Desktop, the Linux VM running Docker Engine is paused, the current state of all your containers are saved in memory, and all processes are frozen. This reduces the CPU usage and helps you retain a longer battery life on your laptop. You can resume Docker Desktop when you want by clicking the **Resume** option. -From the Docker menu, select![whale menu](../images/whale-x.png){: .inline} and then **Pause** to pause Docker Desktop. +From the Docker menu, select![whale menu](images/whale-x.png){: .inline} and then **Pause** to pause Docker Desktop. Docker Desktop displays the paused status on the Docker menu and on the **Containers**, **Images**, **Volumes**, and **Dev Environment** screens in Docker Dashboard. You can still access the **Preferences** (or **Settings** if you are a Windows user) and the **Troubleshoot** menu from the Dashboard when you've paused Docker Desktop. diff --git a/desktop/images/dashboard.PNG b/desktop/images/dashboard.PNG new file mode 100644 index 0000000000000000000000000000000000000000..cdf5c1f8782327d93a6ba884f681cc96d3ace3d3 GIT binary patch literal 30890 zcmdpecTiL7*DjVL76cWgC=fe(L=aF~fY`87^e9SbQ4j;tYiLP4(v*4>q(f8$ln#N= z6R8mbM5L2Igb1M}0RjmmB;0K|zi;jz_m4aC&D=5r*<_RK{g(Bv_gT++)_!rz^y<#- z`?rgUiS4|8?ebq@Vw(|SVjG*bZUN3PJ2Pe>d&Ct{TS`%it{c&K;H{q1Aonm$(%U=a&08k!f^}%v z%UefWKJB@3ajVLiYg%%lyJYx>RVSaEr=C7C(XX7JnWv03^abadBFO<=vzP0}?>ZQ+ zeveOC)-_)?OfgSd%UWO4Rs@hE)9~E}tj+>y!3nPU9Ci>KY7PYnU# zMZj)0?eLQoXmFiy#T&%F>90hrFT{_aIcdE24a9)Gg2UYFxZ(%2P%xtdL0GyelvjqH zZ&+x-#~{<0L1JQ#-3a^?Rw#c8`l(?=h<|}hV1fr_$GUVE>xgb8=#0 z=WmKAvTMHk9ZOWW<~XULIm{Y|=yuvlWVcF;6Vx9Pb+a?h-zO zuBzk24z;cj^y0gqT2SBwkui?yciWfb$Yd3SgCCkd#gZQ=14FO@Q|i6Yj3>u#1LmTf zT|0AgWCx8CQ(c9r07r6G4(8wrJ}(yxkN*w<-rF52H+5t6)VG%i|@Z1?u&gey{9omdW^jMVi>_Fqy(gP49bQ zdUT9qWoL@M?5tI}sF*MxS?EB5slW}W+m3yCK^_=Flt_nyV>rGHS(rk|+#t~TqFVes zlO=LD=oPMk&=rEVSvDI@6hZ{Ov}`6XTQb3RLFC?bIAYq2N*-p;=p#o0HlKruCPT0W zI>PF8D=98~VQu~tq2fS8E;uQNarwX5{e0SbVtUR2$Y1u(^gItoAmF=aWg?hYk%$6D&Q0q`;KVi z=RY~}D{INdIHpaAlQ{RSc&)qs`~w71i+xS9*2Gh#%zm@j`LyvpALihgq$@GP-euVI zz`|QHx;BVZkEYO+)|;1-L6C04S$GD!YFyLFqVzREE@nCnF#U7Rh{)h?nk4vKFq@5X z`EvYX=7L#z!=1{uW_$-%on*NcF$rgNY|OmlGufp=UG3jAf)#NFYAJcdH3NhLvl8*# zBNs%s>47{Enh_L9%u3(=O&K6jNb&m%O?r(P@wGzsn+ zHJCJH_;?5^g}702XJf{K5IK0KN;8d{E9JwB%T;V>Xv`QYcYgeq?|Jc~iG60*x*x(s zgZ*A%A|xRUtlT7iYLi%bak?&+Nxt2c4n3wSXh#(Z<|}Jt>v;!+>^bE`65nd#Gw8hn zoSFW&rtgy>D0qRBK^Ep;sI9^XUG##8;-}o%fSKk$OGk?93w8oyGk^EcRivNsnuO}# z`(eZ9Y}^zQ66PK7bM1z?LZfS%Hji~(+8Q$g&>U1a{BYq&<`B2|fH#z}2FH_IDTJ-) z$%nV<@eO#&9Ao{2)c*b<1(vZJWc~r~B_BJ4=Q52bX3@BFC_7ZBW<0GMy=FYHaGv*4 zJcpMH@g3Ai=fxBooRvUqnQgn2I!lq2hAzWRnFbNytXtXXZ9O#D z=HooHMwgx3NZc-a8Qb0qZC|11vdMdVIvV4gF!@cd4(~)L`KAN?jvOAy~V>#~n!+9n@Y zg&R-=vX;ueQKe}Z1#f{Ggg9J;ga?8bZ+(!8eM~nMTWlq~=2pa&zwfvP7)wvgC8JcL4mzx8?tDB6|89)B zQG%V)26^vi9i_k`Ze$ajKAlzHTKc$0OQ+fczBjU?>7S$2lNUZm-g@NUYK**MhD_|d zToDYaQW2_%pQAr@9AtZd6Zr*=84p466QN)+v7@S!4$v0dSl4ZcKzYZB*msgP{o!B^ zdHSQf8h`LO^<-u4%qPbRlQC24vgNKgr2Ry;)x_1Rrnl)+aF&Yr$=XnGpIJrh+4PjO zWy})v5lM<%KBTZ~=f*ePxGwY-66hTDV{1UD2jfJN!|4e5hZGOEUyulUcq&D{*x3{9 zU4_+ebs#bCg@Tt?uJV!uI+j)RG8M6>TqFNINrpD%q%zk2EjvqNYfKEnS6*-P?-p?H4o+06!AUBJ|+JlbL?`; zmc3D=SNx}0QffJ4#Iu9R85J5j`H!o~$$p(l?M!A59~Wce)$yCYR#iRP?fsFz&@A=GTS%b|ax!D4w4&_@KK2DyfwgkpLF_4qZfBiXF;nn% zWrib*XB;?1*e`ql`k;Rg`Du}VCP&AmN_qzCRfM7mozhAj@1yKi3rxl~y&lR17Excy z$rkd6fqRpbClRv36_=nUs+?pjAv#+cbQE3Me-Q0)axsaJVV z^Vgwsgs(IMm}N8~3G3H*8^66?TSxGC@eZa>V~3HU^oDDz@|b0fm6WhE*Q+#lI<=E8 zja=Pwq5bUKNeFGFF{J6115+-S|KPac^ML;MFyfla8>6Z_8}k=?&`%dLn-pPTl44)* zQAlWi5iAUq@Xz#TSeVkou5a+&y}*oROWj441PNlgS@UD2Lh~ttm;DIwNq5oO%AY=x z({f{y%1#P0iY+|r)$Fs5I+=QV<>g_cXG;}g6}noic^1DHX{;Bte`PUu!ORIuCY4>> zmNf2-xQAR0Fjm8myc0a8!9^>^`|r*faUT+QZ#M_wgB_QLz-ILik)Q5}gVVZ(x0R}4 zkrGz{#FNe4%?iZ`nu@a@Hgy+DBFfG9Gr4iz(U>%VxGd?uhkD8O+>mSe=#!|KdtGv z9rV8A`Yu-bCYtc8nlE7`M?d)6_h!R5Bt}tMOiYJ_=NMs3LZUbayE<0K01I?W19r($ zb{TRz5g0#ZJnyvtuODS%hk+9}iiugy)9~Mld*+|@*rd}MT0b4kzt=cmFej9+TSGME| z(I))WeS)u*b{oVzGF!CIXABO!$6P2?3qBP;2*k+(e{^d*4Lu3VZnzp{XJwyePq7C*5^OPz{NIczHUP1OPLt~D z9D^{p!IeKefCtW;r-y>SloU(>e>z5ai0@C_X8?T6bvNsLQ`tKpW_feEQPI)j-V$)K z+^A~PPEw>25V+vBBHlcNb_2o77nw21vnraT90 zJx4|juu>OVZ9Q=0z<_}rIh2Lu*&0FFYDpHXdW>CjGqd0In3WP>7r(|yWCu+jDQj#9 zc?tcpWL2rm`8FQu!B`iRG33D!(vzt@@IG1EA_}C^i^DRboc%)1(840$=&#Zc9eLHDDIRS3^ zu-Pb!L~38`QCEY#N_4yF9&n()u+oKQS35%%wW)<2V8_#6?0P?|N;r}xn{%k`HP3|cKFsu;FnQUcSyhus-i(-o(%_>jl(IwAY9Eav^I7Zd{{1oTeSyjX zdpV2F#ta+2UU=Ln03VNNE6judz95mix}*SwpoE@2cJ%si|KC@ssNwOy^6SXwX00mM6s0oHb9JT5h$|-)jij}x^NNGpcll`G!>~g=*{0DlO8y_6& zsu&=Y27S*0LHt8XZ`|a65-`g z-7u&X4sL^L3~6vm-G=bn5oO2DWiDyr_qA zJ+lHU?ApP*@}nS(?_Qpod?>hy)M;0@3caz+&#g?__+d3Lmr}ylz!_C>rUuq+cFc#@%SGOY!*Y5ND)I{}3i1oSMap{E8K_eAe5)DZXD_{4cQfvZ- z9;IQBRvJ>Kw)d7Id_z5QYZ9hXhTvZdcIv*`Mb{ZK-Ip27+{=0d?>b77=vsn0k(jI) zh`aJOLhR{hk#okWfqbv|QlB6nnU3BZ)G6mg_NKH)qpg}Rw%BKUZ2IU}+spW1Qpgs( zWi9S(Fg@|mWQ9POZ!nx{Tk8cG4;-Ox5YwT>?q#j@5|GBrkH@BzmIsw{glspNcM^QG zHDbaBO36wsqAyyN1>|?M`VKkQ)_z^}C@XshDKEU3FdTX2vFeVq{b33~UlSpr{`)6Y z8uPHbS;n1}zHWp=W+*LEo(FtCZfUGlu@9=5zwzZU=f;eEq+*fr8^DRu1G3&cF|X2e z@}5xap@pEX-mtjSm}c^0!Wop8jT!5d^;yAH_q~3+m0bO-puzREbrS)t({*Gbn>Hk` zfv^!)wFw!%+G-UB;kC9D1Fy2!kw(R;svphEP}`~Z2b@))#QD21!xeG_PV&f=3%?p9 z;r|$3B0;_aRb;7jJ@^>%+9@sj%j3345BSI;_SUf-cUl{IwUQi`c|_!uH<|><@aQ`l z3rg!o;WHg}e@%D*AIXNcAoSJx)qV_KvE+W1{_G!WtRmFNvQXP;#J`8a+ry%+%}oXM zK=tUFL01~cr^#uiX@BTskLZ7%W(<%ZbwS_zdfYdp6%jOaZo-2nyUsqZSxfBpPgJE? zYL9-sTEV*Tq2h^dS60E4RMB?lGIAIccldltN`%HVoHeIRy*|(l9`b;zyOO>+5Ix{e zS|TojC}+36c>3_6QB{xl+4xnuhrP_6&Lp#@IPt@4eyWy3&jBF41dnxD1 z3mw4qQH0cc&yrmXgyrYP?p9ETkqy=H`-CmG!(>iLkiQOnK`HD~JVb@6+&TI84PRXM z7wHSX60h>QJ2Adi^eePVo?d z+`Vv{&H4aW`jj*MV64l$xV|W8NzK5QFxJ)n#(wN_Q^uaTyR)>Jj*JF>tOs0wbU4Q~ zvy;8rk-DeIWNC8+E=VJ679yTtZF|#RSG3A_d<3CU_O`Uj$76)i; zI1tlz=yVJjP_GlgB`2vV(*mgM9#5r5ztGITUIldC<*x{^d)-(L3kKtJMs|oe>}8H< z02FkY_kn1r&O|FuT#9Zwc<>~=FoE>?#+Tb&E>O|=iHb2(sM)@}gqt63?9yE4<^k@4 zv(QgZDTh*sm!m6Faq3Is)}MbND}|HP)p^(mrGABHJ1WFp)%V)}xZu{ajIEyIh!iDK z%OZm2eTa!h94q>#`uW3 z57pnW4CqL2QN1W;5)hm>}sF_S5yNx>F~_L1r^o%3%jW z!A8b$t3zI&+S-0KaPBnqq+u|*enb<)YZP6Iry~I7af7njFAP}5^AOiD_`eA{qCKet z^{cuBssY1S(Y9LQ1c6#VSHD_U&mROK07f5# z0FfqbHj7hOcP4w?cqfB`)3x)JWI;ha-fCYt-!et2N@JcCera(_Ix!49jD-qlbl$Fm zl;qa=6EBS%yN?885V61U-Cp62s2ru|Iz5ke16;j(<{zUU}qh5cqf5iN^;bS7&N;T#H@RhB@y%l#l&H_Go|e zt?B{sCEPIPBUJhmg9`sc`_1-7P4~rLt2>jfzoGRQjI%04-=&ASoGY|kx3ffQomWgS zb~Cee!B^WdzO^t)*cU+YewAjnpShe@>vN-`#Wt<_k4jCBR+BwMQXDQ9qb-5pBk#6W zdx439V+q2#C$;zHNPmx6ToiuC`_&TtkP^ntX%VY+4CB$~{qA;K1Qn@<8guCGBB|rF zv-(;gvZq59O#5wI5w4;w$_84c>oPszag}yH!N=8dwzx;$bA|tPB+9;);uS*t9?n#n zBR{F0AU4h?OC+Yb!h{xjB6|6gJ4}LaT=B=cb(BlIeQ7fOanLKmw)zJ34-}L290`$( zIZ_3pb(L7`0z-lyox|Blgbb%Xr=LNqkoi{CY%PQEKZW%1dIyOJP zTp^9@uwJ+xg!2=?XZJ_f(`Y?-2C22YyDAY^S;_aT|Cks~(dO4$v~h*=3%5>JE_zl3 zrVF)*wEPNTiyS^LvOM_fJ8rOes&OceuBy9gBR)KB|1s4VPabn-tYvUkSLcH|)wT3veKz>7%>3Fd#{>y3yiOjDA0 z1CYen`MPA$X-l|Gl{6=_zf-?=%cZm|;w77xVIj z-$hq%!g3RS2Ajf$*RorM!s+THi~X2>9abPe@E!4aXf~%!Nk7l4LkKa}H&BX61DNof2Z7Brg)mvnvC^iMWrW2xrixOG1!oJh;xPh5rp-2=63t1%?y7e z>Zn_@J!&I}K6UuzxR-$jbo-3a;^F?;LUys$RR}(h{8rA{fIG3gge_O-6sHUBp)jnXJWJ-;p@#{P}Ze zJ?0{~UFhzkZF8;;z5kcn1X->V0~ebu57a$Ph6Z}gn467rociJyze<}HxGzh0Eg4-j zNYo&p-hm*~W<;ES!!0$)IYr*0mwl;PIK|M`eZ+kz)?8?sOO%(sDR6D^Aq&Cai>^uahF^JqL*<+G*(!a{+7g~kHf?rk=Wt|0p(ntPrRUv6n6S-O+u9B5#9XQDA+( zTbvOrie9!7L?}m3#?_lpv=dm2C&)Wkhx__PHz3Oz`IW95x(^lMsx!KL?yp{ZId}Jt z12j;qb^*FTP3?|>(g2ejAjm321VGGZ6)P2~nIF04e4P^lPp_aexQ4(afz4b`^8FZe zpQlY_+$#qe^woQ=v^kX8mBxfq9*Q9__i>M}z@;C_xy-RqtQ1DTY^#mSy${ zqlr)&Y#72Jj^;2ASXN?^Tvn^{*u{#ZDfPcv%j!BBJ?corKM$ZsX#PR=qbs7t8mzF= zg14v6y}zn(QFo&M@EEDWd-HWY|>YXy(qim+k&@%ff7C zUTcYdvC_J~{w&Uwh%9SM1#${oOmAa8YT|*=vg;`j{GANCXtDf0-r(rv03fsHS4Q4@USm#FIL`0sBp4Ld&bU-+zEKgWkgBlw{@Y`9^U zuUYFIp`VoDBe!mpdjE?yt<#27&FKCih_O`z zzSq(>B&S4so{2T53=LeXn=ec%DiA;cZNKbRK1so z(>206)`Gd!Qt5|^!b-T^7r)16irQ+3pt%D{wq1<-NM78>7|>mCjpD2QRtDiii`W2l z5vratSGy1>z?l<5rrYoz`zggiq#6Ym(q&sSx~mdiSAnY@9PEx2HZfEBgK+G2Emc>6 zqo{nnZDq9F|44N?`5kj=;dY$!N_tsICmsVDNXE}_>x3TZ>akUHC#(8LT=Oe}oXH4R#ArX@6x3wB)W zU5n0GsDo}jTlFY^z2p(#-oqamkz259&A!(bj_L+qv|W7%C#$mjFy0IAp7iZ7Fs)u* zu3ocC&mxHol^P$4wqTBBs+qPM`4_}Ii~YuyNmu!meNfGe61+PX@DTAvTVz`R1IQIX zTIH=Ht4#HjxVl!acOgOwQAVsB*fiG^gFxp0pf#!-4OiOSbLe_If8{Ew{Z;uo7>aP}h^p0|o-ln6|6l2o#QIS1 zZtB|iEG5hquu+HX{HKTi#_EbJ>y;H4BFS*_qthErnGI&;WWH{m70e6DYo2A9G8zK@ z4cNV^q~T-wygvw)3(*;+N%)!JazfS~)~6@G?{OpyT#W9)%qh(5^-Lril1Jsk!3ab# za;B$tU=-<$FskS}HL9M%igX)QqWj@neUvPF7<^de?Dik8lbEosr;ei-DAi z{-R7nFC1HYf#V$fa6jx)qoQiruY47$Ypg3viIZ^lgKi$fdZBhY5cfI^+*ER`G5Pi< z4M`XNuE#n>0T}wz90IKIombA6va+?cGLv$yGm11J@%Ag zh_V$K7pusMR?AP7<5sU#>qd#N%M+8xf;t5WuG%Sn6W?tJRtzGXp9D+SN52t*^oE%Dy4-F#N64Te$S>1Lm&Cgsy&7> z$m2=A=B*dLSgQ7n1A_=DP$_}pX%S$A{#pGf_;{AK{#nQYxNcR-7Ndy*ML7G%CHuO@ zOoLws$b3~W4-PlOWx6saIx_gLK8lPpm*K3?RXsj8zX|gw))k5zIXnoeu-VKoU)6ux$Bd>aNG#6AfekxhRC zZ1&C(9?GuZIu+;OHgjX|96;6RG0Ie6g>LoFTw7v9KZ_b^p0Lm!UFs@d@3C(=230K{ zj|RxW62EPT<5xf*tRr++8Pmp_-T>U3IqXLdngIs=a92$=e;6{O);DYvsz(%VUuu#= zi@NRxYDuME{B7y>VPM9k^mdP@vjDA++RsH%P z=E#t~4(0b!zAA}O4PGl2U_HwK!7I%FYcY=m7rL=otO~RGg4%J#p*ow52gW3s?f+pq ztA$8}-%khUfi1)Y_tFKZGEt>3!`F01}D<^#zzK$q!(bQFWulUXO>qY9^~P<*+wk9@yQU5YFFi(SepAlvb6^87t( zl6zQnbR0$CK=<}*XA%vk2Lu5`DMTLDd&^rB9iy?XMEGRFKk#XnBRbE1JJSn|84Ub4 zUQH!+txI&EY=)xl4g%5-W^N|WQsQe=oO3uCo3|vcU5c2{1q0&X^s`7un zu9Nmj9_+FBuIt@sS%5;uzj_VQxaNhj=})4MmBL@ye{rz~DcWfsIy0{8|0*#oCOeNS z#0F9z|LQdo1F+j7vPQXPzf~Pi9Rw)s>dPP&(@ofe;EntBZ|OQU)+PEy#cUEQae=vO zvHfY{HJG*Ps|eb1NraUC^nG-eUjcjldN3ktDWW;9kJ2O4OI4gvu&7MRFA~hIQFcY#`_(Rx?Pi^(o>zp~%J%s6znd}; z^$*HKvObj#9PSj37RjWRWG+}7=c(0m?~s^cPeXKAX`MRG@H_r@y1oq&hrqi(Sg+1N zk_92NqhFBx9?VTj=GigHTD_fPrYp=O+Yxc_!ha0{sQ>Jse1r_o<^<0Q?9I3{k`K}x z8l?qZKupIT`fKw=AjwtbA1ipQsY;0aHW?>cDV$!rHC!jmVBcW4pK46duA2^Lx#L$R zR?Dl9fQUq~9K83(%}$S*-ZVW*UHviwV%l=^oNEzOzaTx3PBgF!&oufTxEKqq;uJYn z>R=fu?EMw9WUsbKv!;X^A#%X*;ny5nc;9h;K!@)Lk~6(qWhYt1a=XQq+06D$A1x4s zwN_?ka-4%6{=zy(Gp!wZUXxQA5xmA>rkfpzwXXq0yAjBZpH?f1fxM;%r?%LCxmAnu z{NS;TuU%|+yS76O-0LS4L%uN@fz+7JY;Gp#&~0iQ_UYmCk*nQ?lP%>smp-W6-_}6w@G;MhqIO%O!qAx5qMP1&p(zWS zKI!^UwbK@K!3+B7$WhbVh6rWVvG&Oy)8adJeVb*w&;;J!T(?KYs7m^6*NR5*p1FiK zxiX~wL$^K%LQ8x0u-3-o(OCqQSHp;d+Z0C!qx)rEE7|~;cE-8^8iww|Gl&S zjsP2AH|j616A7;uu(Iq+^Qxkv^B&dpPv-#Y~m8lyDgbOPN54XD=^Y+as)h z6XdJ-tiT0qVHn-5auw-|W)Ub{_;J$U3|MzYq9vs>V`N5{IV z*cU!)NM7O#=nKbNNe)_JU?iyLmdl3%$N}`8tug(Y1eN^MEn;(w&d0i%3}rN{J4DJP zR?~Of`HTH%4f(rn(EG68H7Q20{BRHlNu2{_>l$X_buR z^>FPGovrSzaMo6YjuX(@lU+=pu|wLPDdwSPJ+(|XpM@r4+vC;HZtL>;yZ0EuJQIK5 z`w{-DM+Ro~MYWnvwVaI@3dz?KYml@9(=)ec%+KY3kU5mF!U+bEz={y7g*mtkr_=H$`GM0 zN7HY-AWdfn{N$9yk&PJ#+ymi+;LuCzg)H>_-N3^9XX`EiZkn-egLoxOl<}rySo4E3@a%Q~Z#?f$w3Bj+UWvQCK6b2ryDded|HHl-nP=#pM<*w3|OK^%_VkWpDmT80LoXJK_q4+4m%o(# zY4Jj9ImN&eqB=CZmzChRd$_kJ#3RBcBhiCV2@CYaTwm)V6`3+H#{j^4(fY~04JPSf z-pdu}UNrcg;`hCt+xnwWj69JGW*5mw5WgL95i}o7&Iuq!<$J!KhZ}v{<=TVw)Y`na zlzP)G;}2s88vvCu8Sa(?j-rC%ma3Z&Yyd|@M2-&I>~>}2i-N`@wbb#0?jf2OI~!ry zsz!Z7;H=o`RwZ5pNiDY1BhbKodM+QOkWI6esrk?F%ru2OJfk6T22g4?e!w);jh>x{ z8gd-Yy6*CE0aU}E9P|=*{{4A(V}{1)g5eDDR!&3(owkb=&86oR`-nf~O#S1oMY{j) z>ZdzsEwa{Ol^0*$i|W$(9G}RoRx?_@U;ZLTO{0CuVKHN-CpMTtaVkfs5AOp8TFog6 z+QPm>NAR6r!Kup%t#MQITKXf1f(uH`}yre<_j8Jrx`a<|R{B9qv<5_%5^5Y9P>a8p4Jqe*^ zH%Yz1*a7TgP-3ZCoU?*h4A*8UCERg#=cXjW?5NG#%; zrMe?zAM<7~#lc*5j<7T72L+u|wvc`g+Knw#@lW+QDJ^z(`U}u~IOhjcF=JdJ0T9A_ z%pNmmcKHRbWdUsXK-U>@Z|)fN!Jd_vftB%vg)X&9+f3uIwR z$lcs9WH=bM%3TtLMerRb8^hX|&|5t;B^BwMLuCEllz=g~G6^z&3-RzP!{7FEtGA_t z5gC^QZq z)Rge;boJ2bvg`Aui(lUyee=QLp^;bkO?=U9n$vu#oiN1r(OB=KtF@$iVo0tl@8Jkz z*aP05!*-r9glS1wmw5nXV)g7a>ZmR?g}bi@XyKg1n_r7G(C@a*pXOWr#NJ%bo#;HC zE)Kv^Qx)pa_hx|3n6vP_Vto8rf}!pH(oJc!8pqa55apR${pfM*v|_;3-@{ zfuvPp7d7P%J)|R+o&t84J9?o9GnQiTLwzLk8!EdqJQzO#i8DFy_IiNc?)d_Kc!Bvl zyD!CspA&=)yH-Qp@w+(-NQ}2y9pq5f@6%_Erurb4Yc372~;zrU@$s_t` zjCJvmRmdu=-a$*riF+TL63sEy*q|!x;W>Gm)Ym^fG9V^)7aMEc@RXnwOiWFie~m$LHD#1wudjwJ{D!e`!8u3^MI?#fmxVzL87a zvbPC!{KmnTe`s8e9+X4(~xJ0N**MrG!78nGK7c=qmI zY?jvnUbG(>U6X!mk{)vhZ>sWWgQ>~^*IB2MsDKr(-H+(Hg+Btp2SbX8wEzU!fS1F0 zDtw_A6-b)&^Z|V86VEF@39ykL+Zr!1jW!gatvz~Hs0d$fX1nO>J#MP8f|K7HK z4APJAi;vwl9+Ru-|6u)H(L4Ol5J^j6#I`Zxopq+U>QH3yr8rV)Y|!++Xd8ZFaqbxD zderjc-)%W4>#jqOe&)}S$86g;XVz=poAiM32v{g5$6w_yx>^hc>l8T~`lI*b)5|T~ zf9^m(74Ke$$0QXRv7^GivrlzTmf~F$a-shQp-m|=@UP9;evy{^q5HcAPyP;o z{|)v2pO)1BcQ8*ApU1kyS#<|=9zvPS!@m?{;~oFa1qYBQw*X>L&3zjoKciU#`h!m_ z{6zyooDaWW?Y?U5cXT6A)$mP!*U!2Dh_mf->HzOT=WG$-Z4g@#UH#he0I9hQim9z( zOJi7W>ru6Q0LS;IS27La6zE*t*4!w%r#_c9J?{T$`sgpMRDS{>F->zp9Uo?asR4{y z8rsda*`>A~w$dnDOEj369^tKjAxr^*stsovv(^i*0j;OpthHKS8VTVN(4A-|e)gdh z8x8NlEU(G#%t;d2+fJWC5rxB55G~5GToTecmbsD~;pOrUsd7K(YONzA)3yMdGf{f` z0Ho-%YfyC4id=JP;4EcSJ^5aA98&j+ui|6k>1KPzC6Fjzgc!lA+<{yvQ+J5NVC@D{ z^DB`fwAOb;QGewwuYJ9G&;6~!z*k-#cS5Im?UGV_)T)0`Zd?*6)@Zlj1X#v_;6Svi z8|`_LMBktg`zt_)9-->ixmH%9Zd(ynKR0H4<-$S2s?{A7jp91TSO>cyjr!1y>cvYx zY6S*IiilNpV;^WAqG_Sc_6Kv|L>>{v|7t5dp4V}Jx10$c)pnQdAqq<~T;n`HV!b5B zGO96GgMC~-08T)!CV|e#%XH|-9>G}*IM7_8u>ub*1hyri- zJ;edO`&qpcX>sBJ5HZ#_r!7Oq4Kh62l+ z==QgxfEW3m8Aeaf6ACZ`iU0Eq)Ln~}eYM; zues8uY%S*>?Z?kf50&2n&6?QjMa5crzb(q}RNUul@LG6Z~H17@SF}92>2|DBK*8lSzC|2Or*s%c)JaHxKC_>?ez-#@e4KN*Z>w)NgPUHfu>L10ZvRFsL zlVCbu$JI|)>C@ORh6!`7F{6p%7etEsvY2zoHoA33pZVX$Nc7rqi0xeK4(e7(yFde1 z>HuI%wLg}$_Wu0X+XjVo(OSg(LEhfT&kLBomX5)~uBMt(q}Jt^@Xr6BS$ zUDNFPTf9(P_a&A#@io%|wbrN;q~5{$G5!`UD76cw&nccS?v+(O6U*Vc>&60ugJC3#2#QhLZ)B2Y5+8Q&u_o| zpJp#d^;g;0?jS?)a`jP=TO!+w|}LkLB0Bcp(Jvfkv^yY%+|nA=18P zI_74;CG$izWFny8g-wSrU4o+RX-PuR%y6`TZodcjakge;#l(YJ3=%ID`70#&rM3FV zC{|3iwi^~YpBnBL6qlbAoB>PD#yUgYdOV*8bmKc9*8%fa5EQYLSwxKqxljwXXJbYc zi0G*w`@gV$C4ys&Y|g~apwFTmP}}BKV8vShSjdg}qwflX@Q{ENTqgEajp@1S)CL+>pzkfd#OA>=~vS!`vKXxdhs0HM3~^W zoO}a9FAeu43eOI4{ly}FON0BjA|%OCIAAYidPkcjVZHPZd&r3&PT6C5S>PhV2k2u| zW5v@=e<2^Z$u>k$P}9y4CR+4&;bjUk0$jP?V#Am;>Ik5Waz3lOVeErz(qGeGW(>W0 zvAUe1qTESe_3_mI=JW4V|Jc&`ZzfOJ4HcLH1&P0@W{lD9ugy@M+Ff%$l7_#CB(|Tt`p>@wlGdBafxP=Y=O^Dc^UFNH;Qy_m zWPBPoPE~oT>(up47xORR%h(ikGrMel;(bdXcEQ7<*uV4Kh?)LOnFyhUrv3g9aXZ2d z#cir(2M!K$YSQ9yH{Akkd7tyyos5j9wM8gvo=s9cuJ%+4;u?S{!D-DuE~Ud>!&1a6 z7DZt84GQzlFYq}56qwxxGU_Tpi4F~5y{j;O;pm|T7Qe- zAx45g$tI~n>nh+uD2;P|Le6WlXr!FLGZ-|fJ%yBTpuctfox>BNCry#ucAH|RlKdFy zG?s?lm7@Zdusi%g9%*Yv2u{H%d=9O_6atSuAheXPH>4QS=W`@|xbiIEStY#2D##8v zpk)G{Akto$l(?EZV0#_WNhOoO+|r#fJhT50g+A;J0ePE z1VIc0Q3xu%7)l^fkVI-gY9Ikgq=p1TAR+y}sI$&l|8?(O>#lV^oU`tH&4)MdexJRc z{p{ygc2jns_?ekbII z)Yk%-CA{}vqFQ*zQpe4X`F2TWSoDKDq4pDz>H{8r|`d2j6Jpo4tOR^BP0O_*$DY_ z`SZ@viwis{WWlgbl@{w_Dc_SYrsOrdU657~O^K5we-<_uBSjnzemno$a+-2SS@ZJapqX+sH;scbvuaD(Q*{S;T|FN22 zsS8~VlF+lGJ$8s*%?GMc8=E2ex9RxL2>zS9>vcB0DR^4ur{()-IPLNkt*lMmdne%E zj)OSJffc8=#H9uL+38s5G1uzceM9z0G=~xwB^7p5T-_X(Pnrv#G7fbjxpFcB{c5=} zB(a6>@M=K&xbyq@ltSg!mL}xKFOnf$UU3%_&0T0>OnzG#HY2bhpzC0I^7yNqIyT|a z@rP%R-QQ^4yR*5*e)R_Qu_RaU#Hq6Kw>cV3uG5C@atj0M4M;jvozpuE5G{yg7O1*~ ziL_2(J$Mq(Any2aCf-7yPZ8WGtrIO;CHYklIv=_q8LQ}&gfEYIFD43f zt9^#BFR-e2_p)EYp=P3_K&Y7c>DYZB&t1_zsqGo;X6DOM^`m}<(NY4943*9RlPc^m zNU}7E&k;)nQI7a=CptVwcz)=9s@jK6CPtz;UEfcS9k8*T+i=CLANR}O)yLh#5YdCS zl&=Pg*37Vpe#%G&&V8JnBON?%k@n6iWzFtgY5R^km=&+yP&kx!cKN$Uely|(^;G0~ zBCO#T*FX71hrBkL6mo^WSjCkZ7e9)(##G2>&gzpkGu_p1tazW>AQ+)UW=L9dZe&<< zRq=8j2=Pu}YmR)2XO2(`*i--_{K#SiBa#u~e3xiP>ATSxDZl|FF35IZp9;IpSj?io zE1mDn2;>8=XsI$ier~A^sFz&#rgw;}mB0(;IrfH?ZUU%fc)vqCk#upK*^xAxxNz${TeY{Hc>YK^qY>;f>@Zeg;kdZw@{_w1e ze}`dh^scIwiGY_O1`+8^*}K5Dlf;BsN`_(OTd=L}&_^jZ)3W@MFc_06qGfOFPkYa} zUp?|!QF()Fnwd_*zL1&A1^ZT%MuKY!0jdtW4opWhqq zk+Tzrq{qF2J0qEX6;WZH4P0r??7`R>_brHNAe!7oFYQn1K_|6$^p<+J1@*r4^dH?t z6E^Rs32VvVNQBj~93_xdEzI=*i@L`>3UmcBDw_li?sMlG{C&dejH^+T=L)kk*ofB2 zrC{`$02!-*<7TNp=>jp9V2hrC*fU=yAI6UkD?;*1c?UzchfxtlfY}&GCDaBdR(sfbB4P7 zL|jKaxZh)b4yI8f5fP_k-H~3}uf=YYAt0f%K!9N8a-I}KHp~gxig-t)5iH)VcLgc8 zDSJ&wYY@fqiyp5vh*e`fowpJbr#aA)PEQQ>$PA`d0!D^_HHfSza3?MH1@l0AoLGNB_s*MW}ZFs+l#J;VKvNk_%T9cbguR|bDR5bLZ-QrLa_ zk!ZGzTXoedT`xf1>m68y5}%6>$3g?02E5@Dwht6^uqV4N457%-($d!h?!LokNm@OC zw#bj>H-h!+U;L$57%-5KhyN-B%}QB8V4Ac~7d+bVwHRQTSx?*3b%+vj1PmcR{M*v0 zQgQ418lv6WC`?q-DqbLjKLg7V-7HX95A0%TZBJU`Y~MRo$MW1mr-!q8^Su|%N>UHt zRjGBx)QW)2pZ%7I{-*4(w3`8vSgY`fjyc4v;Y0@X-kLCmdl{hC-2%$92BURv=hP`D zA1ZJrw%q0UdI89G$_(Na{O;k%Z^kOeNPuFXgi_Jg4<$XLm-fL?lf_ED&Wp9zGL1u# zjuxt5tJr!utdvlR|5^?162}`plOP&Fz-T6(bDoerMx{+&@wS4$91mRMfIN6l?*&yW zMeq8wcCiYTAVSmS)3vIRL?n5Xzrt~~4RI+EX%4{`gn~j^w?fM83^aRQbx=IT(Ey%Z z4}ZPt?(zFp+~+1DDM~)=cV~LTw_d^Vsw7-_d(239-*AlsZWipzYV~cy`2D?tl>qe5 z5roPRN8 zt;~w#^%pC-@tO_c`Qq|PVlDn_AdGb|mhaUm?G2inAsotdsg{B~c~5V}dHQFB6@;pN zuzwIZUX=av?r-@WF`3upHD_WDA(Z1k10|8BE*gL;hY4o%lMRnqzHOZ2xDq?uEOhVB zc5~Hw&WSQLkXv3 z`9K{=+%Q~cyFDT#x`o(KCyvh`7URE~k3s~hp5Jb9?g-$B5gCyvlHIB+y;#we54H+$ zs&Q(}iWAm#ycLr#Dy~Uf7rnge38bOCqb=Qghe*a$3G;Pzcy=%q{;B_IOS(rfm@;;>L`sbILbtLfLic(bf$z-vHi;Z%#uBy(I4ww1YcsX_VWU+$z_J zt}zEXAvCpx z&CZz`mJ3P=$jdY@f61*@op!z4jwRVrMUksnC`ue+N{gj0nlDI4fC?s$7xaIBZJ_LZ zB|EhTyjo~JC+s=;X&DLo%gHNhGh-IRt@b(j+XY34LT0$ex!X^TLlTGvYJdxv5%A5i zS<@Aq;Ec$lXSehg1%ZIXR!CAlAYuxTFY#Z?OXo@wCT-|0#JXoPhC7FSQ21D&ED^IH zz0znGI^?Y2U1weCF@VdfdP&HB40^3~=8xWMHBOx*pw{nEvXm|xSoQ2_Ocu=- zEqNgC36)_D`SQ2(#&Y0mFQ@~h64E;5&tl?(K<10R!@BQ+Gb4M(>SKjgbHGc!Bf2g< zg|KCKml4RH2dWD4C2Gh6drBcC~ato9MM zMtre;edk47+!o^y6PTCTy<=e*$p^e4P>L}r1(^9xj+IxqoFHed^MV@t$2cm?n_=sUwZqF7-h6O_cRHsyaMA za7CnFN-*>IZaI`=Iv)4s)!;-N6X3#c?T;7PmNEoO#>L0?%e{%Nu&bU6R)+R+&77nt zrfTvpotUC@m+X#8wuJc*0bgUhj=pfq@kWMZCLYLmF;0SP7euXK3L-fnD8b7uLx_bv z+c;UjaveKQSSP}3E?A{gDtT*oh|GlW!>GK{Ye8KxwV!%Ljy9d zz1xd3ibtLe3WsRv(~@3Hc#lGqLoxjJ$s2-8ODBd7V#$)L>g->v!!)4XP2i`M{<{XL z0K;a->-x3&8K;V#drmYr=OFgT;3-l$R3*;ES@VR zatcRCHQG5=8>P+Gu>C6(YFtw`b0lAg5_752P|cn~%yw@FeykN>YeC*>y|~bXFUCu} zQLK`BeYAN*8?SDzZuTAB1E8+&u6UW43iy5K?QF47XaOHK6>U|7Fwf>=h%?8}C&vYM z69D}~l=j|ciz{yJny8Qjh)65(C~yWg(mDcIRsyTq1f!ne+gx8`5M*7N^}$5tZpwki zXZE)`Xux{@VdJA*uKn(mCw%Vu@JA09NC{q&o-iV7#(^a_SfH8NDigQP6|f1kF2x@~S9dqipJuFeUnYc(?Fs%@wDT`Jp;JzZ zW|10BhLs0tNrWqz8|xDRVtYBJ4i)Z&#%)zlP#OONV18dcD81)(X0lW%`j~+_uk!NL z)m=rgp3%J4F26YbnOJYxr$QL;O@lW94Mka+S!!&xoyhWhjfuy=4&Ue5(-Fc0P2qOr z^F#K>bAATdbSE=EoVzpQ|t{?l}@KfLS0Tw7$w7GC;fgd0F#*Y$Sl zI;Uv-Zg%!roSQZ&O~`5lY+g>FFS4tZqi2Tw5cUA?<9%RwUYM>DjB&j%C#Ki0VV(^g z6#$}HVb$3o(sd(ky&f6HPOckIs7n`0J^{;qwq{dW2*Os&ZjtX{?@ z4dx_W;7}T$<%c{|{0*AZypJ|5eoF=`U)$2wc^e%!d}`QAL$komc_D10*)Q76_1I61 z&!%*hd|D+QjoH`b`^Fs1a6q?1;bzYjz?6m}!+X~Hvf`27awrA&K1TsR9U9cQzg-Qw z-sE2q>FIhsQKI&2OD#78B=0=r^m;Yv=YK4DEl(+Z|J%FQUxUXlCN?|^de8?Ft!a?l3P1K_d#vU%u<-vq0NA_Y>|&@ zd_EOac8QLojq1=^aEU!XSq9gO!gL$ab20*GY8Bc`s!H(?ZnZSBnOMfrRp2T99$yZD zH3PO?{wQif5dH=4_A*koAbFqGurEvpC4%pO+m_7lTQ#wjk`bw8{$<5f*MWOhL8O*9 zsXsk*oNLr}z19o(W<4uLzKEANVY+R^57nd1M-qbMRvf_c6~yMN%_4$_uV9e;5B8+|XZZg^%tQYP)IWjxpI~zP&piESp8hjWf8f6Vls*4l zt+@ZmQvYPBf3np77g=ij2?!}))b7F>d;{(m_+6;jZBX+)i6I3Bo6eG>3c@l3(Dr?w>U2HrU<-XGEXA(iO6HX&^f5$1v@7f*m7quNcYgt>=C zxAFG!Favb!XJB`J#XwZFGB$CzuFYl9^iW8&@Bp>mFbY86whesTT}p@s&y^H{s-I;% z&ILsfB$ug~7kw-q@be|6JwBP=`-jud?5c}L99Kmmr^C_E;n1ky_`aBlwqBoy z_!)U z-7jje&iim?fyhvelH`_*7@$@?2G>J*{&9K=&<$x?CqNI2Tm?(^S8X~s`*><|){Va2 zUQB;$j_)gf=;JjsQ0-X0G)cKQZ9&~#p1Z+TUnykXz`Sj#&M68z2-D*t2v6X;8Oe@3YXCo5h8cQ$1RLhp zL~rBHD$Q|1ml_)yAVRcKLlBrZCX2pn?l%;f(}0IX^m&a^ZJ4j-vQC0M1ia{mW~jAt zD-iKE7(xWOdk6BQ(j04xv<_(VY+#@`zM>)Xvz4-4c0;B#sLI|Mb8qzMp9c(y^&pkq zq&oiwTXFq0Vo*)$;?rMLf`*D`@nC185`?giJa_ovOZ-{dhVso?~CXGPb1k3yFzdk;0Oxl&y*X* zukpVdGRSOKFc!^=$=MD8GMRTedQ0^r!O+mRL z_xYDdSWJYa;fV)oAv1yF5iu#pYkF=@dM;IRL=<>l{IL3*<^z)(q@GX_8ns9qwG>K+ zD6~E}dswyoN_L4@^p&3qp2ywL&a#Jg&-pJ+99TDcRz-f958E`!Q|Hax^dIr>0L|9H z;qk?m?HU4YK>%O?aL1N+AJ$HSX(Ym~s_rAqR=PduRgJ*QcQ*4{TcYS55GmmBeDu^ePGns3xcSSHZie+ zZB)A5#R&FIL-X!dqx7+Is0%t-yol?YVQ0}nkE-h+8su5T(BwQATHU}4Y@qr?MM-{b zWyV;ig=T zlwcYL@Q@};Yk5IAbB5j5q0aFYFGuaAzxyxktsEeZZEMhbPTcS|JzE~05?BeDD3o1B zVPTRx)-I^XIvV5g5O0g)F88A7>5j4I=IOfErXP=gdK0~>MyDnOKEWk!J zNk`p{WK+9S0+CqY3b?339COoF>rP$L3P)UfR~QKJCfrVJ0UL<*j$jwThT;;8mjMX< zr&h+y;6X#D$2zg=4EjO5`{Lbzac#n-ez@Zad_EZKfdBTdrA;5Ir+KvbV6K$ zFU!)8;Wou(R;;!jmJ0kN8jr>0l(%fhlt6fUdeA{w^`CvszVJ#iY2J9T+_g%dr_S=i zm;>I@P=QVP1Q%~z(zj?s(`8jh8yzT`s@$FdfEj$4Y+HF;$a+fds{yE!z9;N%i}9TS zrD-1j`FK+e$|eaZJNba8hN=tRfo-l2&SY-n9Nq!eoqP?@FC6-HLq7dTlFnF`NwT?L zlb`KX6Qmk$9R0%kau_U{cR*jZ^gHqnWa1=2**2t*`xRzz>O=FbkFN9V=YwUcK30jt z&tUspk)0bb_vM| z7s&)a@&U}iXCB`;S6YDBrIqNdKXmT{0RSUqgReQ1AwUg7FOOfhb78#upy<2#cah>8!EtRELav+?U&1_4%6-y7i9WcT# zl4%!PJ+0VA{5VDf$ytdESqN!V{8yo@elssjH_tcG}k0LjYrkMWV#C*42{C9NZ i|Evc2noO62>Qg4JsWp{h0jY$->5~p8N{(H={l5UQhTaJP literal 0 HcmV?d00001 diff --git a/desktop/install/images/docker-tutorial-linux.png b/desktop/images/docker-tutorial-linux.png similarity index 100% rename from desktop/install/images/docker-tutorial-linux.png rename to desktop/images/docker-tutorial-linux.png diff --git a/desktop/index.md b/desktop/index.md index 8ea44d3a39ae..02edd4b74daa 100644 --- a/desktop/index.md +++ b/desktop/index.md @@ -1,11 +1,12 @@ --- description: Docker Desktop overview -keywords: Desktop, Docker, GUI, run, docker, local, machine +keywords: Desktop, Docker, GUI, run, docker, local, machine, dashboard title: Docker Desktop overview redirect_from: - /desktop/opensource/ - /docker-for-mac/opensource/ - /docker-for-windows/opensource/ +- /desktop/dashboard/ --- > **Update to the Docker Desktop terms** @@ -16,7 +17,9 @@ redirect_from: {: .important} Docker Desktop is an easy-to-install application for your Mac or Windows environment -that enables you to build and share containerized applications and microservices. +that enables you to build and share containerized applications and microservices. + +It provides a simple interface that enables you to manage your containers, applications, and images directly from your machine without having to use the CLI to perform core actions. Docker Desktop includes: @@ -33,17 +36,34 @@ gives you access to a vast library of certified images and templates in their environment to rapidly auto-build, continuously integrate, and collaborate using a secure repository. -### Key features of Docker Desktop: - -* Ability to containerize and share any application on any cloud platform, in multiple languages and frameworks -* Easy installation and setup of a complete Docker development environment -* Includes the latest version of Kubernetes -* Automatic updates to keep you up to date and secure -* On Windows, the ability to toggle between Linux and Windows Server environments to build applications -* Fast and reliable performance with native Windows Hyper-V virtualization -* Ability to work natively on Linux through WSL 2 on Windows machines -* Volume mounting for code and data, including file change notifications and easy access to running containers on the localhost network -* In-container development and debugging with supported IDEs +## Overview of Docker Dashboard + +When you open Docker Desktop, the Docker Dashboard displays. + +![dashboard](images/dashboard.PNG){:width="750px"} + +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](use-desktop/container.md). + +The **Images** view displays a list of your Docker images and allows you to run an image as a container, pull the latest version of an image from Docker Hub, and inspect images. It also displays a summary of the vulnerability scanning report using Snyk. In addition, the **Images** view contains clean-up options to remove unwanted images from the disk to reclaim space. If you are logged in, you can also see the images you and your organization have shared on Docker Hub. For more information, see [Explore your images](use-desktop/images.md) + +The **Volumes** view displays a list of volumes and allows you to easily create and delete volumes and see which ones are being used. For more information, see [Explore volumes](use-desktop/volumes.md). + +In addition, the Docker Dashboard allows you to: + +- Easily navigate to the **Preferences** (**Settings** in Windows) menu to configure Docker Desktop preferences. Select the **Preferences** or **Settings** icon in the Dashboard header. +- Access the **Troubleshoot** menu to debug and perform restart operations. Select the **Troubleshoot** icon in the Dashboard header. + +### Other key features of Docker Desktop: + +* Ability to containerize and share any application on any cloud platform, in multiple languages and frameworks. +* Easy installation and setup of a complete Docker development environment. +* Includes the latest version of Kubernetes. +* Automatic updates to keep you up to date and secure. +* On Windows, the ability to toggle between Linux and Windows Server environments to build applications. +* Fast and reliable performance with native Windows Hyper-V virtualization. +* Ability to work natively on Linux through WSL 2 on Windows machines. +* Volume mounting for code and data, including file change notifications and easy access to running containers on the localhost network. +* In-container development and debugging with supported IDEs. ## Download and install diff --git a/desktop/install/linux-install.md b/desktop/install/linux-install.md index 6f365aa984d5..0e2d94c090b0 100644 --- a/desktop/install/linux-install.md +++ b/desktop/install/linux-install.md @@ -6,7 +6,7 @@ redirect_from: - /desktop/linux/install/ --- -Welcome to Docker Desktop for Linux. This page contains information about system requirements, download URLs, and instructions on how to install and update Docker Desktop for Linux. + This page contains information about system requirements, download URLs, and instructions on how to install and update Docker Desktop for Linux. > Download Docker Desktop for Linux packages > @@ -216,16 +216,6 @@ Current context is now "desktop-linux" Refer to the [Docker Context documentation](../../engine/context/working-with-contexts.md) for more details. - -## Quick Start Guide - - If you've just installed the app, Docker Desktop launches the Quick Start Guide. The tutorial includes a simple exercise to build an example Docker image, run it as a container, push and save the image to Docker Hub. - - ![Docker Quick Start tutorial](images/docker-tutorial-linux.png) - -Congratulations! You are now successfully running Docker Desktop. Click the Docker menu (![whale menu](images/whale-x.png){: .inline}) to see -**Settings** and other options. To run the Quick Start Guide on demand, select the Docker menu and then choose **Quick Start Guide**. - ## Updates Once a new version for Docker Desktop is released, the Docker UI shows a notification. diff --git a/desktop/install/mac-install.md b/desktop/install/mac-install.md index 8fbf98a36d15..7e8e28366f2f 100644 --- a/desktop/install/mac-install.md +++ b/desktop/install/mac-install.md @@ -103,15 +103,6 @@ The `install` command accepts the following flags: - `--accept-license`: accepts the [Docker Subscription Service Agreement](https://www.docker.com/legal/docker-subscription-service-agreement){: target="_blank" rel="noopener" class="_"} now, rather than requiring it to be accepted when the application is first run - `--allowed-org=`: requires the user to sign in and be part of the specified Docker Hub organization when running the application -### Quick start guide - - If you've just installed the app, Docker Desktop launches the Quick Start Guide. The tutorial includes a simple exercise to build an example Docker image, run it as a container, push and save the image to Docker Hub. - - ![Docker Quick Start tutorial](images/docker-tutorial-mac.png) - -Congratulations! You are now successfully running Docker Desktop. Click the Docker menu (![whale menu](images/whale-x.png){: .inline}) to see -**Preferences** and other options. To run the Quick Start Guide on demand, select the Docker menu and then choose **Quick Start Guide**. - ## Updates {% include desktop-update.md %} diff --git a/desktop/install/windows-install.md b/desktop/install/windows-install.md index 586f3dfe0164..d448c60448ee 100644 --- a/desktop/install/windows-install.md +++ b/desktop/install/windows-install.md @@ -180,16 +180,6 @@ Docker Desktop does not start automatically after installation. To start Docker For more information, see [Docker Desktop License Agreement](../../subscription/index.md#docker-desktop-license-agreement). We recommend that you also read the [Blog](https://www.docker.com/blog/updating-product-subscriptions/){: target="_blank" rel="noopener" class="_" id="dkr_docs_desktop_install_btl"} and [FAQs](https://www.docker.com/pricing/faq){: target="_blank" rel="noopener" class="_" id="dkr_docs_desktop_install_btl"} to learn how companies using Docker Desktop may be affected. -### Quick Start Guide - -When the initialization is complete, Docker Desktop launches the **Quick Start Guide**. This tutorial includes a simple exercise to build an example Docker image, run it as a container, push and save the image to Docker Hub. - -To run the Quick Start Guide on demand, right-click the Docker icon in the Notifications area (or System tray) to open the Docker Desktop menu and then select **Quick Start Guide**. - -![Docker Quick Start tutorial](images/docker-tutorial-win.png){:width="450px"} - -Congratulations! You are now successfully running Docker Desktop on Windows. - ## Updates {% include desktop-update.md %} diff --git a/desktop/use-desktop/volumes.md b/desktop/use-desktop/volumes.md index d12703e14b40..cd286c0af6f2 100644 --- a/desktop/use-desktop/volumes.md +++ b/desktop/use-desktop/volumes.md @@ -3,30 +3,36 @@ description: Docker Dashboard keywords: Docker Dashboard, manage, containers, gui, dashboard, images, user manual title: Explore Volumes --- -## Explore volumes -You can use [volumes](../../storage/volumes.md) to store files and share them among containers. Volumes are created and are directly managed by Docker. They are also the preferred mechanism to persist data in Docker containers and services. - -> **Volume Management is now available for all subscriptions** -> -> Starting with Docker Desktop 4.1.0 release, Volume management is available for users on any subscription, including Docker Personal. Update Docker Desktop to 4.1.0 to start managing your volumes for free. -{: .important} The **Volumes** view in Docker Dashboard enables you to easily create and delete volumes and see which ones are being used. You can also see which container is using a specific volume and explore the files and folders in your volumes. -### Manage volumes +For more information about volumes, see [Use volumes](../../storage/volumes.md) By default, the **Volumes** view displays a list of all the volumes. Volumes that are currently used by a container display the **In Use** badge. -Use the **Search** field to search for any specific volumes. You can also sort volumes by the name, the date created, and the size of the volume. +## Manage your volumes + +Use the **Search** field to search for any specific volumes. + +You can sort volumes by: +- Name +- Date created +- Size + +From the **More options** menu to the right of the search bar, you can choose what volume information to display. + +## Examine a volume To explore the details of a specific volume, select a volume from the list. This opens the detailed view. The **In Use** tab displays the name of the container using the volume, the image name, the port number used by the container, and the target. A target is a path inside a container that gives access to the files in the volume. -The **Data** tab displays the files and folders in the volume and their file size. To save a file or a folder, hover over the file or folder and click on the more options menu. Select **Save As** and then specify a location to download the file. +The **Data** tab displays the files and folders in the volume and the file size. To save a file or a folder, hover over the file or folder and click on the more options menu. Select **Save As** and then specify a location to download the file. -To delete a file or a folder from the volume, select **Remove** from the more options menu. +To delete a file or a folder from the volume, select **Remove** from the **More options** menu. ### Remove a volume -Removing a volume deletes the volume and all its data. To remove a volume, hover over the volume and then click the **Delete** button. Alternatively, select the volume from the list and then click the **Delete** button. \ No newline at end of file +Removing a volume deletes the volume and all its data. + +To remove a volume, hover over the volume and then click the **Delete** icon. Alternatively, select the volume from the list and then click the **Delete** button. \ No newline at end of file From a2bc1c6f6dc716652ce2d1b32287a2bbde94e737 Mon Sep 17 00:00:00 2001 From: Allie Sadler <102604716+aevesdocker@users.noreply.github.com> Date: Tue, 19 Jul 2022 13:08:45 +0100 Subject: [PATCH 6/6] fixes --- desktop/faqs/general.md | 2 +- desktop/linux/troubleshoot.md | 2 +- desktop/use-desktop/container.md | 79 +++------------------- desktop/use-desktop/images.md | 112 +++++++++++++++---------------- desktop/use-desktop/volumes.md | 4 +- 5 files changed, 71 insertions(+), 128 deletions(-) diff --git a/desktop/faqs/general.md b/desktop/faqs/general.md index 33efa38bdc26..319259b707c8 100644 --- a/desktop/faqs/general.md +++ b/desktop/faqs/general.md @@ -42,7 +42,7 @@ cannot access features that require an active internet connection. Additionally, any functionality that requires you to sign won't work while using Docker Desktop offline or in air-gapped environments. This includes: -- The in-app [Quick Start Guide](../install/mac-install.md#quick-start-guide) +- The in-app [Quick Start Guide](../get-started.md#quick-start-guide) - Pulling or pushing an image to Docker Hub - [Image Access Management](../../docker-hub/image-access-management.md) - [Vulnerability scanning](../../docker-hub/vulnerability-scanning.md) diff --git a/desktop/linux/troubleshoot.md b/desktop/linux/troubleshoot.md index d7326ec179df..ec8316a10ebd 100644 --- a/desktop/linux/troubleshoot.md +++ b/desktop/linux/troubleshoot.md @@ -57,7 +57,7 @@ Before you get started, we recommend that you sign into your Docker Desktop appl 6. If you have a paid Docker subscription, click **Contact Support**. This opens the [Docker Desktop support](https://hub.docker.com/support/desktop/){:target="_blank" rel="noopener" class="_"} form. Fill in the information required and add the ID you copied earlier to the Diagnostics ID field. Click **Submit** to request Docker Desktop support. > **Note** > - > You must be signed in to Docker Desktop using your Pro, Team, or Business tier credentials to access the support form. For information on what's covered as part of Docker Desktop support, see [Support](#support). + > You must be signed in to Docker Desktop using your Pro, Team, or Business tier credentials to access the support form. For information on what's covered as part of Docker Desktop support, see [Support](../support.md). 7. If you don't have a paid Docker subscription, you can click **Upgrade to benefit from Docker Support** to upgrade your existing account. Alternatively, click **Report a Bug** to open a new Docker Desktop issue on GitHub. This opens Docker Desktop [for Linux](https://github.com/docker/desktop-linux/issues/) on GitHub in your web browser in a 'New issue' template. Complete the information required and ensure you add the diagnostic ID you copied earlier. Click **submit new issue** to create a new issue. diff --git a/desktop/use-desktop/container.md b/desktop/use-desktop/container.md index e715a4d09666..ccf9874aef07 100644 --- a/desktop/use-desktop/container.md +++ b/desktop/use-desktop/container.md @@ -4,83 +4,28 @@ keywords: Docker Dashboard, manage, containers, gui, dashboard, images, user man title: Explore Containers --- -The **Containers** tab lists all your running containers and applications. You must have running or stopped containers and applications to see them listed. +The **Containers** view lists all your running containers and applications. You must have running or stopped containers and applications to see them listed. -The following sections guide you through the process of creating a sample Redis container and a sample application to demonstrate the core functionalities in Docker Dashboard. +## Container actions -### Start a Redis container +Use the **Search** field to search for any specific container. -To start a Redis container, open your preferred CLI and run the following command: - -`docker run -dt redis` - -This creates a new Redis container. From the Docker menu, select **Dashboard** to see the new Redis container. - -### Start a sample application - -Let's start a sample application. Download the [Example voting app](https://github.com/dockersamples/example-voting-app) from the Docker samples page. The example voting app is a distributed application that runs across multiple Docker containers. The app contains: - -- A front-end web app in [Python](https://github.com/dockersamples/example-voting-app/blob/master/vote) or [ASP.NET Core](https://github.com/dockersamples/example-voting-app/blob/master/vote/dotnet) which lets you vote between two options -- A [Redis](https://hub.docker.com/_/redis/) or [NATS](https://hub.docker.com/_/nats/) queue which collects new votes -- A [.NET Core](https://github.com/dockersamples/example-voting-app/blob/master/worker/src/Worker), [Java](https://github.com/dockersamples/example-voting-app/blob/master/worker/src/main) or [.NET Core 2.1](https://github.com/dockersamples/example-voting-app/blob/master/worker/dotnet) worker which consumes votes and stores them -- A [Postgres](https://hub.docker.com/_/postgres/) or [TiDB](https://hub.docker.com/r/dockersamples/tidb/tags/) database backed by a Docker volume -- A [Node.js](https://github.com/dockersamples/example-voting-app/blob/master/result) or [ASP.NET Core SignalR](https://github.com/dockersamples/example-voting-app/blob/master/result/dotnet) web app which shows the results of the voting in real time - -To start the application, navigate to the directory containing the example voting application in the CLI and run `docker-compose up --build`. - -```console -$ docker-compose up --build -Creating network "example-voting-app-master_front-tier" with the default driver -Creating network "example-voting-app-master_back-tier" with the default driver -Creating volume "example-voting-app-master_db-data" with default driver -Building vote -Step 1/7 : FROM python:2.7-alpine -2.7-alpine: Pulling from library/python -Digest: sha256:d2cc8451e799d4a75819661329ea6e0d3e13b3dadd56420e25fcb8601ff6ba49 -Status: Downloaded newer image for python:2.7-alpine - ---> 1bf48bb21060 -Step 2/7 : WORKDIR /app - -... -Successfully built 69da1319c6ce -Successfully tagged example-voting-app-master_worker:latest -Creating example-voting-app-master_vote_1 ... done -Creating example-voting-app-master_result_1 ... done -Creating db ... done -Creating redis ... done -Creating example-voting-app-master_worker_1 ... done -Attaching to db, redis, example-voting-app-master_result_1, example-voting-app-master_vote_1, example-voting-app-master_worker_1 -... -``` - -When the application starts successfully, from the Docker menu, select **Dashboard** to see the Example voting application. Expand the application to see the containers running inside the application. - -Now that you can see the list of running containers and applications on the Dashboard, let us explore some of the actions you can perform: - -- Click **Port** to open the port exposed by the container in a browser. -- Click **CLI** to open a terminal and run commands on the container. If you have installed iTerm2 on your Mac, the CLI option opens an iTerm2 terminal. Otherwise, it opens the Terminal app on Mac, or a Command Prompt on Windows. -- Click **Stop**, **Start**, **Restart**, or **Delete** to perform lifecycle operations on the container. - -Use the **Search** option to search for a specific object. You can also sort your containers and applications using various options. Click the **Sort by** drop-down to see a list of available options. - -### Interact with containers and applications - -From the Docker Dashboard, select the example voting application we started earlier. - -The **Containers** view lists all the containers running on the application and contains a detailed logs view. It also allows you to start, stop, or delete the application. Use the **Search** option at the bottom of the logs view to search application logs for specific events, or select the **Copy** icon to copy the logs to your clipboard. - -From the **Containers** view you can also perform the following actions on multiple containers at once: +From the **Containers** view you can perform the following actions on one or more containers at once: - Pause - Resume - Stop - Start - Delete -Click **Open in Visual Studio Code** to open the application in VS Code. Hover over the list of containers to see some of the core actions you can perform. +When you hover over individual containers, you can also: +- Click **Open in Visual Studio Code** to open the application in VS Code. +- Open the port exposed by the container in a browser. -### Container view +### Inspect a container -Click on a specific container for detailed information about the container. The **container view** displays **Logs**, **Inspect**, and **Stats** tabs and provides quick action buttons to perform various actions. +You can obtain detailed information about the container when you select a container. + +The **container view** displays **Logs**, **Inspect**, and **Stats** tabs and provides quick action buttons to perform various actions. - Select **Logs** to see logs from the container. You can also: - Use `Cmd + f`/`Ctrl + f` to open the search bar and find specific entries. Search matches are highlighted in yellow. @@ -94,5 +39,3 @@ Click on a specific container for detailed information about the container. The - Select **Inspect** to view low-level information about the container. You can see the local path, version number of the image, SHA-256, port mapping, and other details. - Select **Stats** to view information about the container resource utilization. You can see the amount of CPU, disk I/O, memory, and network I/O used by the container. - -You can also use the quick action buttons on the top bar to perform common actions such as opening a CLI to run commands in a container, and perform lifecycle operations such as stop, start, restart, or delete your container. \ No newline at end of file diff --git a/desktop/use-desktop/images.md b/desktop/use-desktop/images.md index 44bcce79cad7..78e39e4eb772 100644 --- a/desktop/use-desktop/images.md +++ b/desktop/use-desktop/images.md @@ -4,105 +4,105 @@ keywords: Docker Dashboard, manage, containers, gui, dashboard, images, user man title: Explore Images --- -The **Images** view is a simple interface that lets you manage Docker images without having to use the CLI. By default, it displays a list of all Docker images on your local disk. To view images in remote repositories, click **Sign in** and connect to Docker Hub. This allows you to collaborate with your team and manage your images directly through Docker Desktop. +The **Images** view is a simple interface that lets you manage Docker images without having to use the CLI. By default, it displays a list of all Docker images on your local disk. -The Images view allows you to perform core operations such as running an image as a container, pulling the latest version of an image from Docker Hub, pushing the image to Docker Hub, and inspecting images. +You can also view images in remote repositories, once you have signed in to Docker Hub. This allows you to collaborate with your team and manage your images directly through Docker Desktop. -In addition, the Images view displays metadata about the image such as the tag, image ID, date when the image was created, and the size of the image. It also displays **In Use** tags next to images used by running and stopped containers. This allows you to review the list of images and use the **Clean up images** option to remove any unwanted images from the disk to reclaim space. +The **Images** view allows you to perform core operations such as running an image as a container, pulling the latest version of an image from Docker Hub, pushing the image to Docker Hub, and inspecting images. -The Images view also allows you to search images on your local disk and sort them using various options. +The **Images** view displays metadata about the image such as the: +- Tag +- Image ID +- Date created +- Size of the image. -Let's explore the various options in the **Images** view. +It also displays **In Use** tags next to images used by running and stopped containers. -If you don’t have any images on your disk, run the command `docker pull redis` in a terminal to pull the latest Redis image. This command pulls the latest Redis image from Docker Hub. +The **Images on disk** status bar displays the number of images and the total disk space used by the images. -Select **Dashboard** > **Images** to see the Redis image. + ## Manage your images -### Run an image as a container + Use the **Search** field to search for any specific image. -Now that you have a Redis image on your disk, let’s run this image as a container: + You can sort images by: +- Name +- Date created +- Size -1. From Docker Dashboard, select **Images**. A list of images on your local disk displays. -2. Select the Redis image from the list and click **Run**. -3. Optional step: When prompted, click the **Optional settings** drop-down to specify a name, port, volumes, environment variables and click **Run**. - To use the defaults, click **Run** without specifying any optional settings. This creates a new container from the Redis image and opens it on the **Containers** view. +## Run an image as a container -### Pull the latest image from Docker Hub +From the **Images view**, hover over an image and click **Run**. -To pull the latest image from Docker Hub: +When prompted you can either: -1. From the Docker menu, select **Dashboard** > **Images**. This displays a list of images on your local disk. -2. Select the image from the list and click the more options button. -3. Click **Pull**. This pulls the latest version of the image from Docker Hub. +- Click the **Optional settings** drop-down to specify a name, port, volumes, environment variables and click **Run** +- Click **Run** without specifying any optional settings. -> **Note** -> -> The repository must exist on Docker Hub in order to pull the latest version of an image. You must be logged in to pull private images. -### Push an image to Docker Hub +## Inspect an image -To push an image to Docker Hub: +Inspecting an image displays detailed information about the image such as the: -1. From the Docker menu, select **Dashboard** > **Images**. This displays a list of images on your local disk. -2. Select the image from the list and click the more options button. -3. Click **Push to Hub.** +- Image history +- Image ID +- Date the image was created +- Size of the imag -> **Note** -> -> You can only push an image to Docker Hub if the image belongs to your Docker ID or your organization. That is, the image must contain the correct username/organization in its tag to be able to push it to Docker Hub. -### Inspect an image +To inspect an image, hover over an image, select the **More options** button and then select **Inspect** from the dropdown menu. -Inspecting an image displays detailed information about the image such as the image history, image ID, the date the image was created, size of the image, etc. To inspect an image: +## Pull the latest image from Docker Hub -1. From the Docker menu, select **Dashboard** > **Images**. This displays a list of images on your local disk. -2. Select the image from the list and click the more options button. -3. Click **Inspect**. -4. The image inspect view also provides options to pull the latest image, push image to Hub, remove the image, or run the image as a container. +Select the image from the list, click the **More options** button and click **Pull**. -### Remove an image +> **Note** +> +> The repository must exist on Docker Hub in order to pull the latest version of an image. You must be logged in to pull private images. -The **Images** view allows you to remove unwanted images from the disk. The Images on disk status bar displays the number of images and the total disk space used by the images. +## Push an image to Docker Hub -You can remove individual images or use the **Clean up** option to delete unused and dangling images. +Select the image from the list, click the **More options** button and click **Push to Hub**. -To remove individual images: +> **Note** +> +> You can only push an image to Docker Hub if the image belongs to your Docker ID or your organization. That is, the image must contain the correct username/organization in its tag to be able to push it to Docker Hub. -1. From the Docker menu, select **Dashboard** > **Images**. This displays a list of images on your local disk. -2. Select the image from the list and click the more options button. -3. Click **Remove**. This removes the image from your disk. +## Remove an image > **Note** > > To remove an image used by a running or a stopped container, you must first remove the associated container. -**To remove unused and dangling images:** -An **unused** image is an image which is not used by any running or stopped containers. An image becomes **dangling** when you build a new version of the image with the same tag. +You can remove individual images or use the **Clean up** option to delete unused and dangling images. + +An unused image is an image which is not used by any running or stopped containers. An image becomes dangling when you build a new version of the image with the same tag. -**To remove an unused or a dangling image:** +To remove individual images, select the image from the list, click the **More options** button and click **Remove** -1. From the Docker menu, select **Dashboard** > **Images**. This displays a list of images on your disk. -2. Select the **Clean up** option from the **Images on disk** status bar. -3. Use the **Unused** and **Dangling** check boxes to select the type of images you would like to remove. +To remove an unused or a dangling image: + +1. Select the **Clean up** option from the **Images on disk** status bar. +2. Use the **Unused** or **Dangling** check boxes to select the type of images you would like to remove. The **Clean up** images status bar displays the total space you can reclaim by removing the selected images. -4. Click **Remove** to confirm. +3.. Select **Remove** to confirm. -### Interact with remote repositories +## Interact with remote repositories -The Images view also allows you to manage and interact with images in remote repositories and lets you switch between organizations. Select an organization from the drop-down to view a list of repositories in your organization. +The **Images** view also allows you to manage and interact with images in remote repositories and lets you switch between organizations. Select an organization from the drop-down to view a list of repositories in your organization. > **Note** > -> If you have a paid Docker subscription and enabled [Vulnerability Scanning](../../docker-hub/vulnerability-scanning.md) in Docker Hub, the scan results will appear on the Remote repositories tab. +> If you have a paid Docker subscription and enabled [Vulnerability Scanning](../../docker-hub/vulnerability-scanning.md) in Docker Hub, the scan results appear on the Remote repositories tab. The **Pull** option allows you to pull the latest version of the image from Docker Hub. The **View in Hub** option opens the Docker Hub page and displays detailed information about the image, such as the OS architecture, size of the image, the date when the image was pushed, and a list of the image layers. To interact with remote repositories: 1. Click the **Remote repositories** tab. 2. Select an organization from the drop-down list. This displays a list of repositories in your organization. -3. Click on an image from the list and then select **Pull** to pull the latest image from the remote repository. -4. To view a detailed information about the image in Docker Hub, select the image and then click **View in Hub**. +3. Hover over an image from the list and then select **Pull** to pull the latest image from the remote repository. + +To view a detailed information about the image in Docker Hub, select the image and then click **View in Hub**. - The **View in Hub** option opens the Docker Hub page and displays detailed information about the image, such as the OS architecture, size of the image, the date when the image was pushed, and a list of the image layers. +The **View in Hub** option opens the Docker Hub page and displays detailed information about the image, such as the OS architecture, size of the image, the date when the image was pushed, and a list of the image layers. - If you have a paid Docker subscription and have enabled [Vulnerability Scanning](../../docker-hub/vulnerability-scanning.md) the Docker Hub page also displays a summary of the vulnerability scan report and provides detailed information about the vulnerabilities identified. \ No newline at end of file +If you have a paid Docker subscription and have enabled [Vulnerability Scanning](../../docker-hub/vulnerability-scanning.md) the Docker Hub page also displays a summary of the vulnerability scan report and provides detailed information about the vulnerabilities identified. diff --git a/desktop/use-desktop/volumes.md b/desktop/use-desktop/volumes.md index cd286c0af6f2..d708f466ab82 100644 --- a/desktop/use-desktop/volumes.md +++ b/desktop/use-desktop/volumes.md @@ -12,7 +12,7 @@ By default, the **Volumes** view displays a list of all the volumes. Volumes tha ## Manage your volumes -Use the **Search** field to search for any specific volumes. +Use the **Search** field to search for any specific volume. You can sort volumes by: - Name @@ -21,7 +21,7 @@ You can sort volumes by: From the **More options** menu to the right of the search bar, you can choose what volume information to display. -## Examine a volume +## Inspect a volume To explore the details of a specific volume, select a volume from the list. This opens the detailed view.