Managing Docker Images in Docker Desktop

An **In Use** tag displays next to images used by running and stopped containers. You can choose what information you want displayed by selecting the **More options** menu to the right of the search bar, and then use the toggle switches according to your preferences. The **Images on disk** status bar displays the number of images and the total disk space used by the images and when this information was last refreshed. ## Manage your images Use the **Search** field to search for any specific image. You can sort images by: - In use - Unused - Dangling ## Run an image as a container From the **Images view**, hover over an image and select **Run**. When prompted you can either: - Select the **Optional settings** drop-down to specify a name, port, volumes, environment variables and select **Run** - Select **Run** without specifying any optional settings. ## Inspect an image To inspect an image, select the image row. Inspecting an image displays detailed information about the image such as the: - Image history - Image ID - Date the image was created - Size of the image - Layers making up the image - Base images used - Vulnerabilities found - Packages inside the image [Docker Scout](/manuals/scout/_index.md) powers this vulnerability information. For more information about this view, see [Image details view](/manuals/scout/explore/image-details-view.md) ## Pull the latest image from Docker Hub Select the image from the list, select the **More options** button and select **Pull**. > [!NOTE] > > The repository must exist on Docker Hub in order to pull the latest version of an image. You must be signed in to pull private images. ## Push an image to Docker Hub Select the image from the list, select the **More options** button and select **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. ## Remove an image > [!NOTE] > > To remove an image used by a running or a stopped container, you must first remove the associated container. 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 individual images, select the bin icon. ## Docker Hub repositories The **Images** view also allows you to manage and interact with images in Docker Hub repositories. By default, when you go to **Images** in Docker Desktop, you see a list of images that exist in your local image store. The **Local** and **Docker Hub repositories** tabs near the top toggles between viewing images in your local image store, and images in remote Docker Hub repositories that you have access to. Switching to the **Docker Hub repositories** tab prompts you to sign in to your Docker Hub account, if you're not already signed in. When signed in, it shows you a list of images in Docker Hub organizations and repositories that you have access to. Select an organization from the drop-down to view a list of repositories for that organization. If you have enabled [Docker Scout](../../scout/_index.md) on the repositories, image analysis results (and [health scores](/manuals/scout/policy/scores.md) if your Docker organization is eligible) appear next to the image tags. Hovering over an image tag reveals two options: - **Pull**: Pull the latest version of the image from Docker Hub. - **View in Hub**: Open the Docker Hub page and display detailed information about the image. ## Additional resources - [What is an image?](/get-started/docker-concepts/the-basics/what-is-an-image.md)

This section describes how to manage Docker images in Docker Desktop using the Images view. It covers actions like running images as containers, inspecting images, pulling the latest versions from Docker Hub, pushing images to Docker Hub, and removing images. It also explains how to filter and sort images, and how to manage images in Docker Hub repositories. Additionally, it mentions Docker Scout integration for vulnerability analysis.