Docker desktop for windows что это

Эта статья даст вам полное представление о Docker Desktop для пользователей Windows и MAC. Мы изучим установку Docker Desktop на компьютерах с Windows и Mac. После установки мы также попытаемся выполнить некоторые операции Docker.

Docker Desktop — это собственное настольное приложение, разработанное Docker для пользователей Windows и MAC. Это самый простой способ запуска, сборки, отладки и тестирования приложений Dockerized.

Docker Desktop предлагает важные и наиболее полезные функции, такие как быстрые циклы редактирования, уведомления об изменениях файлов, встроенная поддержка корпоративной сети и гибкость для работы с собственным выбором прокси и VPN.

Docker Desktop состоит из инструментов для разработчика, приложения Docker, Kubernetes и синхронизации версий. Он позволяет вам создавать сертифицированные образы и шаблоны языков и инструментов.

Скорость, безопасность и выбор — все, что вам нужно для разработки и доставки контейнерных приложений, доступных на вашем рабочем столе, будет представлено вам.

Прежде чем перейти к процессу установки, давайте разберемся с его версиями.

Версии Docker

Docker в основном поставляется в двух версиях, в Community и ENterprise.

Community версия поставляется с бесплатным набором продуктов Docker. ENterprise корпоративная версия представляет собой сертифицированную контейнерную платформу, которая предоставляет коммерческим пользователям дополнительные функции, такие как безопасность образов, управление образами, оркестровка и управление средой выполнения контейнеров, но по разумной цене.

Мы начнем наше обучение с Community Edition. Контейнеры Docker, работающие в конкретной операционной системе, совместно используют ядро ​​ОС. Это означает, что мы не можем использовать ядро ​​Windows (хост) для запуска контейнеров Linux или наоборот. Чтобы проделать это, у нас есть Docker Desktop для Windows и MAC.

Выпуски Docker Desktop

Docker Desktop выпускается в двух вариантах.

• Stable: как видно из названия, стабильный выпуск тщательно протестирован и может быть использован при разработке более надежных приложений. Его версии полностью синхронизированы с версиями Docker Engine.
• Edge: эти версии состоят из всех новых и экспериментальных функций Docker Engine. Есть больше шансов ошибок, сбоев и проблем, которые могут возникнуть. Тем не менее, пользователи получат возможность ознакомиться с предстоящими функциями.

Docker на Windows

Есть два варианта Docker на Windows.

1. Использование Docker Toolbox

Docker Toolbox предоставляет набор легких инструментов.

• Oracle virtual box
• Docker Engine
• Docker Machine
• Docker compose
• Kitematic GUI

Вышеуказанные инструменты устраняют необходимость развертывания отдельной виртуальной машины для запуска Docker. Просто установите исполняемый файл панели инструментов Docker непосредственно в Windows и начните разработку приложений. Требуется 64-битная ОС и Windows 7 или выше с включенным режимом виртуализации.

Но опять же, панель инструментов Docker — это оригинальная поддержка, предоставляемая в Windows для запуска Docker и его устаревшего решения для всех ОС Windows, которые не соответствуют требуемой конфигурации.

2. Использование Docker Desktop

Docker Desktop — это новейшая технология, используемая для Docker в Windows. Он заменяет виртуальную машину Oracle собственной технологией виртуализации, доступной в Windows, то есть Microsoft Hyper-V.

Он по-прежнему будет запускать Docker на Linux-машине, созданной под ним. Но на этот раз вместо виртуальной машины Oracle мы использовали нативный Microsoft Hyper-V.

Установка Docker на Windows

Вы можете скачать репозиторий Docker Desktop из Docker Hub.

истемные требования:

• Windows 10 или Windows Server 2016 Professional или Enterprise Edition
• Поддержка Hyper-V.

Чтобы запустить Hyper-V, оборудование должно соответствовать следующим требованиям:

• 64-битный процессор
• > = 4 ГБ ОЗУ
• Поддержка виртуализации оборудования на уровне BIOS

Следовательно, программная и аппаратная зависимость заключается в запуске Docker Desktop на Windows.

Установка Docker на macOS

Вы можете скачать репозиторий Docker Desktop из Docker Hub.  

Системные требования:

• MAC Hardware 2010 или новее с аппаратной поддержкой управления памятью и неограниченным режимом. Выполните команду kern.hv_support, чтобы проверить, поддерживает ли оборудование MAC инфраструктуру гипервизора.
• MAC OS версии 10.13 или новее.
• > = 4 ГБ ОЗУ
• Virtual-Box до версии 4.3.30

Работа с образами

После установки проверьте версию установленного Docker Engine.

docker --version

Docker работает с доставкой и запуском контейнерных приложений. Вам либо нужно создать свое собственное контейнерное приложение, либо Docker поддерживает контейнерные образы в Docker Hub, и его можно легко загрузить с помощью простой команды docker run.

Здесь мы будем тянуть образ Redis.

docker pull redis

С помощью простой команды run образы можно скачивать и загружать на GitHub или Docker Hub, и любой пользователь во всем мире может получить к нему доступ и начать работать с ним.

Docker Container запускает образ Docker. Следующим шагом является запуск контейнера.

docker run -p 6379 Redis

Будет создан зашифрованный идентификатор контейнера. Вы можете быстро проверить состояние работающего экземпляра в Docker, нажав на Dashboard option.

Обязательно остановите контейнер, прежде чем удалять его из Docker Engine.

Возможности Docker Desktop

Существует множество преимуществ:

• Поддерживает широкий спектр инструментов разработки.
• Обеспечьте быстрый и оптимизированный способ создания и публикации контейнерного образа на любой облачной платформе.
• Простота установки и настройки полной среды Docker
• Повышение производительности благодаря встроенной виртуализации Hyper-V для Windows и HyperKit для MAC.
• Возможность работать в Linux через WSL 2 на компьютерах с Windows.
• Легкий доступ к работающим контейнерам в локальной сети.
• Возможность поделиться любым приложением на облачной платформе, на разных языках и в разных средах.
• Для обеспечения безопасности и актуальности выполняются автоматические обновления.
• Включены последние версии Kubernetes.
• Возможность переключения между Linux и Windows сервером на Windows.

Docker Desktop — это нативное приложение, разработанное на Windows и MAC OS для запуска, сборки и доставки контейнерных приложений или сервисов.

Однако

Docker Desktop предназначен не для производственной среды, а для рабочего стола и среды разработки.

Также рекомендуем прочитать:

1. Docker для начинающих — технология контейнеров
2. В чем разница между Docker и Kubernetes?
3. Введение в Docker Hub и все, что вы должны знать о нем
4. Как установить Docker на Ubuntu, Windows, Debian и CentOS?
5. Kubernetes — Введение для начинающих
6. Docker посмотреть запущенные контейнеры, запустить или остановить контейнеры

What is Docker Desktop & How Does it Work?

It is often imperative to first understand the history behind any tools and tech to understand from where it came and why it was created even in the first place. So to get into history, Docker first saw its light in 2011 in France when Solomon Hykes envisioned building platform-independent mechanisms to deploy all your development binaries in such a way that all the libraries, os level dependencies, and codes can be deployed on any cloud or system giving the developer confidence that their software will function as expected without any rework and hiccups.

The core reason for docker container conceptualization was to make a developer’s life easy. Setting up a working environment configuration to support different software versions on any given machine was a big issue. But with docker, you just need to create an isolated package comprising of all the configurations (called docker container) supporting different versions, and each container here holds a separate isolated environment configuration that doesn’t impact the OS level configs or any other running container active on your machine.

Now that we have some basic idea of why docker was started and created, it’s a high time we define a few components to establish docker as a concept. So the first thing is to define Docker. Know more about devops skills that a devops engineer should master. 

What is Docker?

Docker is like that huge Cargo Ship loaded with big boxes (unique containers to be pulled by the tagged owners) that offers developers a Software platform that allows them to build, test, and deploy applications quickly. Docker packages software into standardized units called containers that have everything the software needs to run including libraries, system tools, code, and runtime.

Docker provides the ability to package and run an application in a loosely isolated environment called a container. The isolation and security allow you to run many containers simultaneously on a given host. 

To further understand the magic of docker we need to decode the Docker architecture as it lays down clearly how each component of the Docker system interacts with the others.

Docker Architecture

Fig 1- Docker Architecture

Docker has three major components:  

• Client 
• Docker Host
• Registry

Let’s dig deeper into each one of these, one by one. First and foremost we need to understand the docker daemon.

If you want to know more about docker and get a practical sense of it, you can explore our dedicated docker online course. 

What Is Docker Deamon?

It is a kind of persistent thread that runs in the background in order to manage the Docker containers on a single host. 

Docker daemon also known as dockerd, runs on the host operating system acting like a runtime that takes care of docker objects like 

• Docker images 
• Docker containers 
• Networks and  
• Storage 

Now that you know the basics of docker daemons let’s understand the first key component of Docker architecture

Docker Client

As it is seen, in Fig 1, the docker client is like your local machine where all the necessary client operations are performed by the users. This client gives developers a primary interface (CLI) to interact with the Docker server (daemons) using the pre-defined set of commands

Its main objective is to provide a medium to direct the pull of images from a registry and to have it run on a Docker host. Common commands issued by a docker client are: 

$ docker build 
$ docker pull 
$ docker run 

Docker client uses these commands and REST APIs to interact with Docker daemon which also is a Server. Do you know that the Docker client can communicate with more than one daemon?

Docker Host

It is a complete hosting environment that holds docker daemon, containers, images, networks, and storage that is required by developers to execute and run any given applications

Docker Registry

The primary role of the docker registry is to store docker images. These image repositories can be either public or private. The popular public registry is the Docker hub.

So whenever you as a developer are looking to pull one of the docker images using the docker pull command, the required images are pulled from your publicly configured registry (like docker hub). Similarly, when you use the docker push command, your image is pushed to your configured registry. 

Before we wrap up the docker fundamentals we also need to touch upon the docker objects.

Docker Objects

You can’t fully understand Docker without understanding the underlying docker objects. Some of the key objects are

• Docker Images
• Docker Containers 

Docker Images

Being a developer you would have for sure came across a situation where the development you have done locally on your PC/Laptop requires you to configure your editor, OS dependencies, libraries, environment variables, etc to package and run your code binary. But if your system breaks down due to some reason and you are asked to move to a new PC/Laptop, that old code binary struggles to run as expected on it.

But in the current time, this is not the case thanks to Docker and a docker objects called Image.

Docker image

It is nothing but a read-only template that has all the instructions required to create a docker container(another object which we will cover next). These images use as a private container registry to share container images either publicly or privately. Every packed image in the container is meta-tagged to explain the container’s ability.

These images are at the core of the Docker ecosystem, as they foster team collaboration and speedy development and deployment. The kind of experience it brings is simply commendable and that’s why Docker images and their underlying utility are so popular in the developer and tech fraternity.

Dockerfile

Being a developer, you may simply use docker images created by someone and shared publicly or maybe want to create a custom image to be used within the organization. While creating a custom image you rely on the concept of Dockerfile which defines a simple syntax comprising the steps needed to create the image and deploy it on Docker hub/ AWS ECR repo.

Dockerfile has all the instructions which are created as a separate layer in the docker image, so whenever you update the docker images only those layers which have changed are rebuilt. This is the reason which makes docker images so lightweight, tiny, and quick as compared to the older concept of virtualization 

Docker Containers

Now that we know the basics of docker images it’s time to decode another key docker object called Containers.

Containers are nothing but the runnable instance of a docker image. 

Runnable is an interface that is to be implemented by a class whose instances are intended to be executed by a thread. 

These containers can be

• Created 
• Started 
• Stopped 
• Moved 
• Deleted

All by the use of Docker CLI/API.

Containers are isolated pieces that can be plugged into one or more networks and also allow storage to be associated with it. Each container that are hosted in Docker Host is unique and is defined by the images it holds as well as by the configs. 

Do you know?  

When a container is deleted, all the changes to its state that are not stored in persistent storage vanishes. 

With this, we have covered all the fundamentals one should before knowing Docker Desktop. So let’s start defining. But before that, get to know more about how to become a devops engineer. 

What Is Docker Desktop?

As we have understood so far that docker objects like images and containers are key building blocks, it is also imperative to know that these objects are generally dockerized, and here the role of Docker Desktop comes into the picture.

Docker desktop is the fastest way to containerize/dockerize applications. It is a native application designed by Docker for both Windows and MAC users. 

Why Docker Desktop?

Docker desktop that is built on top of the Docker engine is a perfect tool for developers that are looking to leverage the Docker ecosystem and get started quickly to dockerize and deploy their apps. It is a powerful tool that packages Docker’s CLI, Docker Compose, Kubernetes, and other tools to Fastrack application development.

It is easy to install and OS independent and comes up with these key features that make it stand out amongst others 

Top Features that Makes Docker Desktop Special

• Simple and easy-to-install providing an environment to build, ship, and run your containers 
• Storage volumes are easily mapped and managed
• Supports both Local and remote management of Docker images 
• Facilitates collaborations amongst developers where they can share repeatable and reproducible development from their local machine to the docker container 
• Easy to get started with Kubernetes on your local machine with Docker Desktop.
• Provides a simple dashboard to help developers get an overview of running containers, images, and volumes 
• Tailor-made to support multi-architecture images 

Now that we have got enough reason to use the Docker desktop it’s time to get decode how one can install it and get started.

Getting Started With Docker Desktop for Windows & Mac

Before we kickstart this phase its important to understand a few things

What are a few things to know?  

• Docker desktop supports both Windows and MAC systems.
• One should use a community open source edition to get started with Docker desktop
• Also, there is a commercial edition that is suitable for enterprises and a large team
• Commercial use of Docker Desktop in larger enterprises (more than 250 employees OR more than $10 million USD in annual revenue) now requires a paid subscription. 

Installing Docker Desktop On Mac

Docker desktop comes with two versions for mac

• One for MAC with Intel Chip
• One For MAC with its own indigenous Apple chip

Pre-requisites Of MAC — Intel Chips :  

• macOS must be version 10.15 or newer. That is, Catalina, Big Sur, or Monterey.
• Run the command kern.hv_support to verify if MAC hardware supports the Hypervisor framework 
• If you experience any issues after upgrading your macOS to version 10.15, you must install the latest version of Docker Desktop to be compatible with this version of macOS. 
• At least 4 GB of RAM. 
• VirtualBox prior to version 4.3.30 must not be installed as it is not compatible with Docker Desktop 

Installing Docker Desktop On MAC — Intel Chip:  

The best way is to visit

Install Docker Desktop on Mac 

Estimated reading time: 7 minutes Update to the Docker Desktop terms Commercial use of Docker Desktop in larger…docs.docker.com 

And download the latest Docker installation file from there, you will get the options as depicted below.

Click for the intel version and wait till the docker .dmg file is downloaded. Once done just click the file and the rest will be an easy cakewalk as the wizard will be there to guide you. You must read and agree on the SLA which will be popping on your MAC to proceed.

Similarly, you can install docker desktop on your MAC with an Apple silicon chip

Pre-requisites Of MAC — Intel Chips : 

• It is recommended that you download the latest Docker Desktop version. With version 4.3.0, the hard requirement to install Rosetta 2 is no more required but still, to get the best-uninterrupted experience, it is wise that you install Rosetta 2.
• One can install Rosetta 2 manually from the CLI, using the following command: 

$softwareupdate --install-rosetta 

Installing Docker Desktop On MAC — Apple Silicon Chip: 

The process through guided wizard remains the same. Download the .dmg file for the Apple silicon version and the rest you can easily set up using Wizard after you have given your consent against the SLA.

Installing on MAC using CLI: (for both chip types it works ) 

Once you have downloaded the preferred .dmg file considering your MAC machine chip type (Intel/Apple silicon) you can easily install the docker desktop via CLI commands as shown below.

You need to type these commands on your mac terminal

$ sudo hdiutil attach Docker.dmg 
$ sudo /Volumes/Docker/Docker.app/Contents/MacOS/install 
$ sudo hdiutil detach /Volumes/Docker 

What is hdiutil? 

hdiutil is a command-line utility in macOS to Manipulate disk images (attach, verify, burn, etc). 

$ sudo /Volumes/Docker/Docker.app/Contents/MacOS/install 

Here install command accepts the following arguments — 

• —accept-license: accepts the Docker Subscription Service Agreement(SLA) now, rather than requiring it to be accepted when the application is first run 
• —allowed-org=<org name>: requires the user to sign in and be part of the specified Docker Hub organization when running the application 

If you are done installing, you may be able to open it by visiting your launchpad and clicking on the docker icon

Once you click, you can see the docker fav menu icon on the extreme top right of your MAC as seen in the image below, in my case you can see a first small icon that starts to animate and you will see the docker desktop dashboard as shown below.

It will show you the current docker images, volumes attached, and the environment info. This means you are now successfully running Docker Desktop. You can click the docker fav menu icon to see Preferences and other options. 

Installing Docker Desktop On Windows

Visit this official docker link — 

Install Docker Desktop on Windows 

Update to the Docker Desktop terms Commercial use of Docker Desktop in larger enterprises (more than 250 employees OR…docs.docker.com 

And select the option as shown below-

Pre-requisite:  

You should take care of the following before installing docker desktop on your windows machine:

• Windows 11 64-bit: Home or Pro version 21H2 or higher, or Enterprise or Education version 21H2 or higher. 
• Windows 10 64-bit: Home or Pro 21H1 (build 19043) or higher, or Enterprise or Education 20H2 (build 19042) or higher. 
• Enable the WSL 2 feature on Windows. For detailed instructions, refer to the Microsoft documentation. 

Windows Subsystem for Linux is a compatibility layer for running Linux binary executables natively on Windows 10, Windows 11, and Windows Server 2019. In May 2019, WSL 2 was announced, introducing important changes such as a real Linux kernel, through a subset of Hyper-V features 

• The following hardware prerequisites are required to successfully run WSL 2 on Windows 10 or Windows 11: 
• 64-bit processor with Second Level Address Translation (SLAT) 
• 4GB system RAM 
• Hyper-V and Containers Windows features must be enabled.(only if you want Hyper-V option instead of WSL 2) 
• BIOS-level hardware virtualization support must be enabled in the BIOS settings. For more information, see Virtualization. 
• Download and install the Linux kernel update package. 

Installing Docker Desktop On Windows Using Wizard:  

1. Double-click Docker Desktop Installer.exe that you downloaded as per the instructions we have covered above in order to run the installer. 
2. When asked, ensure WSL 2 instead of Hyper-V option on the Configuration page is selected. It depends on your choice of backend. 
3. Note in case your PC only supports one of the two options, you will not be able to select which backend to use 
4. Follow the given instructions on the installation wizard to authorize the installer and complete the installation 
5. When the installation is done, click Close to complete the installation process. 

Note! 

If your admin account is different from your user account, you must add the user to the docker-users group.

• Run Computer Management as an administrator and navigate to Local Users and Groups > Groups > docker-users. Right-click to add the user to the group. Log out and log back in for the changes to take effect. 

Installing from the CLI:  

Please ensure Docker Desktop Installer.exe is available locally on your machine. If yes, then type the following command in a terminal. Make sure you are in the root folder where the installer file exists.

«Docker Desktop Installer.exe» install 

In case you use PowerShell you should type 

Start-Process ‘.winbuildDocker Desktop Installer.exe’ -Wait install 

The install command accepts the following arguments : 

• —quiet: suppresses information output when running the installer 
• —accept-license: accepts the Docker Subscription Service Agreement now, rather than requiring it to be accepted when the application is first run 
• —allowed-org=<org name>: requires the user to sign in and be part of the specified Docker Hub organization when running the application 
• —backend=<backend name>: selects the backend to use for Docker Desktop, hyper-v or wsl-2 (default) 

Note! 

In case your admin account is different from your user account, you must add the user to the docker-users group: 

net localgroup docker-users <user> /add 

Now that the installation process has been completed, its time to validate the same 

Start the Docker On Your Machine :  

Start Docker Desktop

To start Docker Desktop 

1. Search for Docker, and select the Docker Desktop menu option in the search results. 
2. Accepts the SLA terms & conditions

Note! 

If you do not agree to the updated terms, the Docker Desktop application will close and you can no longer run Docker Desktop on your machine. You can choose to accept the terms at a later date by opening Docker Desktop. 

3. When the initialization is complete, you can see Quick Start Guide UI as seen in the image below

You can skip it for the time being and move forward. You will be able to view the docker dahsboard. This shows you have successfully installed the docker desktop!.

If you want to install docker desktop on the Linux system, you can easily do so by following the instructions given in the below-given link.

Here is the installation link —  

Install Docker Desktop on Linux 

Welcome to Docker Desktop for Linux. This page contains information about system requirements, download URLs, and…docs.docker.com 

Docker Desktop release notes:  

When you are installing Docker desktop fresh or want to update, do keep a close eye on these release notes that are frequently updated and shared on Docker’s official web portal. Here is the link-

Docker Desktop release notes 

Estimated reading time: 31 minutes This page contains information about the new features, improvements, known issues…docs.docker.com 

This comprises the new features, improvements, known issues, and bug fixes in Docker Desktop releases. 

Quick Workshop To Get You Started

Now that we are done with the installation it’s time to play with the docker desktop. We will learn in this demo a few of the docker commands like

• docker run 
• docker push  
• docker pull 
• docker build  

We will see the pushed docker image in our docker hub public repo. So before we start please sign in to your docker desktop, you need to have an account with docker hub, if not please visit here- 

Docker Hub Container Image Library | App Containerization 

Edit descriptionhub.docker.com 

Firstly, signup. Once you have created the account go to the docker desktop icon and sign-up with the same. Once you signup you will see the below-given screen

1. Docker Run: 

Open your terminal and type this command-

$ docker run hello-world 

When you type there may be a high probability that the image with this name would not be present locally, but don’t worry docker understands this as a default thing so it will look for the docker image with this name in their docker hub public repo and will take a pull to download the same as shown in the image below.

Output:  

You can clearly see that the docker run command looked for the image and as it didn’t find the same, took the pull from the hub.

So now when you again run the docker run command you will see that it responded with the message — 

“Hello from the Docker!” 

2.  Listing all docker images : 

When you key in this command you can see the list of the Docker images that exist in your local system, which can also be seen in your docker desktop dashboard, here is how it looks in my docker dashboard.

3.  Docker ps command: 

The ‘docker ps’ is a Docker command to list the running containers by default 

$ docker ps 

When typed this command this, you can see in the output none of container images are in a running state

But if you want to list all the containers, including stopped once? We can do that by adding —all option. 

$ docker ps - all 

I have created on the image, docker/getting-started, let’s see if it is running state or not

If we type docker ps again let’s see what happens 

$ docker ps 

Now you can see that our latest pulled image docker/getting-started is in a running state.

4. Docker stop command: 

To stop a container, use the docker stop command with either the container id or container name. We may stop a container if we want to change our docker run command. 

Here we will stop our docker/getting-started container whose id is “6fa658d60902” 

$docker stop 6fa658d60902 

Now when we run the ps command after running docker stop, we can see that now our docker/getting-started has stopped.

5. Docker restart Command: 

As can be seen from the above image, after we ran the docker restart command using the command- 

$docker stop 6fa658d60902 

and again typed docker ps command we get our docker/getting-started container up and running again stopped. 

6. Docker Push Command: 

If you want to push your Docker image to any public repository like the docker hub, you can use the docker push command.

Let’s create a public repo in the docker hub. So go to docker and sign-in

Once you give a repo name and click a create button, you will see the following output UI

Our repo with name pramdemo/demorepo is created, also, the command which will be required to push to this new repo is given on the right side-

“docker push pramdemo/demorepo:tagname” 

Let’s see how we can push our locally existing docker images to this docker hub repo now.

When you type

$docker push pramdemo/demorepo 

it will flag an error because no such image exists with the tag pramdemo/demorepo 

Let’s tag our local image docker/getting-started and try to push the same to the docker hub repo 

$ docker tag docker/getting-started pramdemo/demorepo 

Now that we have the tagged image ready let’s try to push the same

$ docker push pramdemo/demorepo 

woohoo! the image got pushed, let. check the same in our docker hub repo 

You can see in the docker hub tag section the image got pushed.

This way you can code all your app create a docker image using dockerfile, and push the same to the docker hub publicly or privately. Once this is done your image will be ready to be pulled by any CI/CD pipeline or by any of your team members.

6. Docker Pull Command: 

Now that your image is pushed in your docker hub repo you can anytime take a pull of the same in your local machine and get started. let’s see how it works.

If you carefully see the pushed image you will also get a pull command that one can use to take a pull. In this case the command is

$ docker pull pramdemo/demorepo:latest 

the output:  

We can see from the CLI output our latest image got pulled successfully.

7. Docker remove Command:

If you wanna get rid of unwanted images from your repo you can do so by command 

docker rmi it removes images by their ID. 

To remove the image, you first need to list all the images to get the Image IDs, Image names, and other details. 

Let’s get the image id of docker/getting-started  

We can see that docker/getting-started has the image id 157095baba98 

So if we type

$ docker rmi 157095baba98 

Output:

We got an error as one of the containers is running which is using this image, so we need to first stop the container or we can also enforce the deletion by using -f flag, let’s do the same and see the outcome 

$docker rmi 157095baba98 -f 

output:  

We can see that our image docker/getting-started that had the image id 157095baba98 got deleted. When we typed the command

we can see that the all the images with the ID 157095baba98 got removed 

Takeaways

We have comprehensively covered the docker and docker desktop journey and can see how magical this tool is. We learned the fundamentals of

• Docker 
• Docker objects 
• Docker architecture
• What & Why of Docker Desktop tool 
• Installation of Docker on Windows and MAC systems 

Then we ran through a quick demo workshop to see a few of the popular docker commands in action.

So what we learned from this, well here are a few key learnings as a takeaway

• Docker is a go-to tool for any big enterprises or small startups to ensure they are building, running, testing, and shipping their binaries fast
• If you are looking for a smart collaboration tool for development docker has to be a part of your arsenal to scale those efforts, especially when you are looking to implement micro-services as a part of your DevOps culture 

To learn more about DevOps you can check one of the best courses for DevOps 

• Docker supports docker-compose & Kubernetes which helps you to orchestrate your containerized apps and deploy them to the K8S cluster at scale.

Want to learn more about Docker and Kubernetes, you can subscribe to this exclusive course called docker and kubernetes online training. 

If you’re new to containers and Docker and work primarily on Windows, you’re in for a treat. In this article, you’re going to learn how to set up Docker on Windows 10 using Docker Desktop for Windows or simply referred to as Docker Desktop in this article.

Not a reader? Watch this related video tutorial!

Not seeing the video? Make sure your ad blocker is disabled.

Docker Desktop is the Docker Engine and a management client packaged together for easy use in Windows 10. In this article, you will install Docker Desktop, deploy your first container, and share data between your host and your containers.

Prerequisites for Docker on Windows

This is a walkthrough article demonstrating various steps in Docker Desktop for Docker on Windows. To follow along, be sure you have a few specific requirements in place first.

• An Internet connection to download 800MB+ of data
• Windows 10 64-bit running Pro, Enterprise, or Education edition with release 1703 or newer. This is necessary to run Hyper-V on Windows 10.
• A CPU with SLAT (nested paging) compatibility. All AMD/Intel processors since approximately 2008 are SLAT compatible
• At least 4GB of RAM
• BIOS hardware virtualization sometimes labeled as Virtualization Technology or VTx. This must be enabled and show as Enabled in the performance tab of Task Manager as shown below.

Downloading and Installing Docker Desktop

Up first, you need to download and install Docker Desktop to get Docker on Windows going. Docker Desktop comes available in two releases; a stable release and a testing release.

The stable release is released quarterly and ensures a fully-tested application. In this article, you will be using the stable release.

Warning: Upon installation, Docker Desktop will prompt you to install the Hyper-V hypervisor if not already installed. By doing so, the Hyper-V hypervisor prevents any user-mode hypervisors such as VirtualBox, VMWare, etc. from running guest VMs. Hyper-V support for VirtualBox and VMWare is limited but coming.

You also have the option of a download source through manually downloading Docker Desktop directly from Docker.com or via the Windows package manager, Chocolatey. Let’s briefly cover each method.

From Docker.com

To download Docker Desktop directly from docker.com, you can go to the product page, register for an account and download it from there. This is preferred if you intend to use Docker in production by registering an account.

However, if you’re just testing Docker out for the first time, you can also download it directly which is much easier.

Once the EXE is downloaded, run the executable and click through the prompts accepting all of the defaults.

When asked whether you plan to Use Windows containers instead of Linux containers, as shown below, do not enable the checkbox. You will be using Linux containers in this article.

Once installation is complete, reboot your computer.

Selecting the option to use Windows containers or Linux containers tells Docker to attach images to a Windows kernel or Linux kernel. You can change this setting at any time after installation by right-clicking the Docker icon in the System Tray and selecting Switch to Windows containers as shown below.

Using Chocolatey

The other option to get Docker Desktop downloaded and installed is with Chocolatey. Chocolatey automates many of the download/install tasks for you. To do so, open up a command-line console (either cmd or PowerShell) as an administrator to download and install the program in one shot by running the command below.

choco install docker-desktop

Once complete, reboot Windows 10.

If you’d like to try out the testing release at some point, you can download and install this by running choco install docker-desktop --pre.

Validating the Docker Desktop Installation

Once installed, Docker Desktop automatically runs as a service providing Docker on Windows. It’s shown in the system tray when you log in to Windows after you reboot. But how do you actually know it’s working?

To validate Docker Desktop is working correctly, open a command-line console and run the docker command. If the installation went well, you will see a Docker command reference.

Finally, have Docker download and run an example container image called hello-world by running the command docker run hello-world. If all is well, you will see output like below.

Running Commands in Docker Containers

Docker Desktop is installed and you’ve verified all is well? Now what? To get started with Docker on Windows, one common task to perform in a Docker container is running commands. Through the docker run command, you can send commands through the host (your Windows 10 PC) directly into a running container.

To run commands in a container with docker run, you’ll first specify an image name followed by the command. To get started, tell Docker to run the command hostname inside of a container called alpine as seen below.

> docker run alpine hostname
b74ff46601af

Since you don’t have the alpine Docker image on your computer now, Docker on Windows will download the tiny image from the Docker Hub, bring up a container from that image, and send the command directly into the container and shut it down all in one swoop.

If you’d like to keep the container running, you can also use the -it parameter. This parameter tells Docker to keep the container in “interactive mode” leaving it running in the foreground after executing the command. You’ll see that you are then presented with a terminal prompt ready to go.

> docker run -it alpine sh
/ #

When you’re done in the terminal, type exit to return to Windows 10.

Accessing Files from the Docker Host in Containers

Another common task is accessing host files from containers. To access host files in containers, Docker on Windows allows you to link a folder path from your desktop to share that folder to your container. This process is called binding.

To create a binding, make a folder on a local drive. For this example, I’ll use E: and call it input. It’ll then create a new text document named file.txt in the folder. Feel free to use whatever path and file you wish.

Once you have the folder you’d like to share between the host and container, Docker needs to mount the folder using the --mount parameter. The --mount parameter requires three arguments; a mount type, a source host directory path and a target directory path. The target path will be a symbolic link within the container.

Below you will see an example of mounting the entire E: within the Windows 10 host to show up as the /home/TEST directory inside of the Linux container.

> docker run --mount type=bind,source="E:/",target=/home/TEST -it alpine

When you attempt to mount a host folder, Docker Desktop will ask for your permission to share this drive with the Docker containers as seen below.

If you created the file.txt file in the Windows 10 folder as described earlier, run cat /home/TEST/input/file.txt. You will see that contents are displayed.

Now, delete the input folder that you just created and run the cat ... command again. Observe that the shell now reports that the file does not exist anymore.

Mapping Network Ports

Another important concept to know is how Docker on Windows handles networking. For a brief introduction, let’s see what it takes to access a web service running in a container from the local host.

First, spin up a demo image that will run an example webpage. Download and run the Docker image called dockersamples/static-site. You’ll use docker container run to do so.

The following command does four actions at once:

• Downloads a Docker image from Docker Hub called static-site in the docker-samples “directory”
• Starts a container instance up from the static-site image
• Immediately detaches the container from the terminal foreground (—detach)
• Makes the running container’s network ports accessible to the Windows 10 host (—publish-all)

docker container run --detach --publish-all dockersamples/static-site
## Alternate/shorthand syntax that does the same thing:
## docker container run -d -P dockersamples/static-site
## docker run -d -P dockersamples/static-site

Once run, Docker will return the container ID that was brought up as shown below.

Publishing Network Ports

Since using the --publish-all parameter, local host ports are now mapped to the container’s network stack. You can use the docker ps subcommand to list all running containers including what ports are assigned to all of the running containers. In the instance below, one container is running mapping host port 32777 to container port 80 and host port 32776 to container port 443.

Docker on Windows assigns containers random ports when using the --publish-all parameter unless explicitly define them.

Now open up a web browser and navigate to http://localhost:32777 or the port that Docker assigned to map to port 80 as output by docker ps. If all goes well, you should see the below webpage show up.

Changing the Published Ports

You now have a Docker container running in Docker on Windows serving up a simple web page. Congratulations! But now you need to specify a specific port binding not relying on the random port selection with --publish-all. No problem. Use the -p parameter.

First, stop the running container by specifying a unique string of it’s container ID. You can find this container ID by running docker ps. Once you know the container ID, stop the container and start a new one while designating Docker to assign a specific port to publish.

The syntax for specifying a port is <external port>:<container port>. For each port that you want to publish, use the --publish or -p switch with the external and container port numbers as shown below.

> docker stop f766
> docker run --detach -p 1337:80 dockersamples/static-site

When you are specifying a container ID, you only have to type enough of the ID to be unique. If you are only running a single container and its ID is f766f4ac8d66bf7, you can identify the container using any number of characters including just f. The requirement is that whatever you type allows it to uniquely identify a single container.

Now go to your web browser and navigate to localhost:1337. Remember, you are not changing the image and it always listens on port 80; you are changing the port translation rule in the Docker configuration that lets you connect to the container.

Stopping all Containers

Using docker stop, you can stop a container but how do you stop multiple containers at once? One way to do so is by providing multiple, space-delimited container IDs. You can see below an example of how to stop three containers with IDs of fd50b0a446e7, 36ee57c3b7da, and 7c45664906ff.

> docker stop fd50 36ee 7c45

If you’re managing Docker containers in PowerShell, you can also use a shortcut to stop all containers. Feed a list of container IDs via docker ps -q to the stop parameter through PowerShell’s command expansion docker stop (docker ps -q).

Confirm all containers are stopped by seeing no containers listed when you type docker ps.

Cleaning Up

You’ve downloaded a few container images and run some containers that are now stopped. Even though they’re stopped, their allocated storage isn’t gone off of the local host disk. You must delete the containers free up that space and avoid cluttering up your workspace.

To delete a single container, use the container remove rm parameter like below.

> docker container rm <container ID>

Or, to delete all stopped containers, use the prune parameter as below.

Рассмотрим установку Docker Desktop for Windows — это Community-версия Docker для систем Microsoft Windows.

Системные требования

• Windows 10 64-bit: Pro, Enterprise, Education (Build 16299 или выше).

Для успешного запуска Client Hyper-V в Windows 10 требуются следующие предварительные требования к оборудованию:

• 64 bit процессор c поддержкой Second Level Address Translation (SLAT).
• 4GB системной памяти.
• Поддержка аппаратной виртуализации на уровне BIOS должна быть включена в настройках BIOS.

Подготовка

Включаем функции Hyper-V Containers Window. Для этого переходим в панель управления — установка и удаление программ — включение или отключение компонентов Windows. Активируем пункт Hyper-V, который включает Hyper-V Managment Tools, Hyper-V Platform.

Также это можно выполнить через powershell или dism (все команды необходимо выполнять с правами администратора).

Powershell:

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All

DISM:

DISM /Online /Enable-Feature /All /FeatureName:Microsoft-Hyper-V

Установка

Скачиваем установщик Docker (Docker Desktop Installer) с Docker Hub.

Установка Docker Desktop включает Docker Engine, Docker CLI client, Docker Compose, Notary, Kubernetes и Credential Helper. Контейнеры и образы, созданные с помощью Docker Desktop, используются всеми учетными записями пользователей на компьютерах, на которых он установлен. Это связано с тем, что все учетные записи Windows используют одну и ту же виртуальную машину для создания и запуска контейнеров. При использовании Docker Desktop WSL 2 невозможно обмениваться контейнерами и образами между учетными записями пользователей.

Запускаем установщик Docker Desktop Installer.exe и ожидаем пока он скачает все необходимые компоненты.

После установки система потребует перезагрузки. Перезагружаемся и входим в систему.

После входа может возникнут запрос на установку дополнительного компонента WSL2. Переходим по ссылке и скачиваем необходимый пакет с официального сайта Microsoft.

После скачивания выполняем установку WSL2, после которой снова потребуется перезагрузка.

Настройка и запуск приложения

Входим в систему и ждем запуска всех служб Docker. Когда все службы будут запущены, мы увидим в трее классический значок Docker — это значит что служба установлена и запущена. Далее можно запустить приложение Docker desktop. Далее можно изменить настройки Docker при необходимости:

Далее управление Docker выполняется через Powershell. Проверяем версию и выполняем тестовый запуск контейнера:

После выполнения всех этих действий, Docker готов к использованию.

Нужна помощь? Настройки docker/docker swarm/docker compose мы осуществляем в рамках услуги DevOps-аутсорсинг.