Orientation and setup

Estimated reading time: 4 minutes

Welcome! We are excited that you want to learn Docker.

This page contains step-by-step instructions on how to get started with Docker. In this tutorial, you’ll learn how to:

• Build and run an image as a container
• Share images using Docker Hub
• Deploy Docker applications using multiple containers with a database
• Running applications using Docker Compose

In addition, you’ll also learn about the best practices for building images, including instructions on how to scan your images for security vulnerabilities.

If you are looking for information on how to containerize an application using your favorite language, see Language-specific getting started guides.

We also recommend the video walkthrough from DockerCon 2020.

Download and install Docker

This tutorial assumes you have a current version of Docker installed on your machine. If you do not have Docker installed, choose your preferred operating system below to download Docker:

Start the tutorial

If you’ve already run the command to get started with the tutorial, congratulations! If not, open a command prompt or bash window, and run the command:

You’ll notice a few flags being used. Here’s some more info on them:

• -d — run the container in detached mode (in the background)
• -p 80:80 — map port 80 of the host to port 80 in the container
• docker/getting-started — the image to use

You can combine single character flags to shorten the full command. As an example, the command above could be written as:

The Docker Dashboard

Before going too far, we want to highlight the Docker Dashboard, which gives you a quick view of the containers running on your machine. The Docker Dashboard is available for Mac and Windows. It gives you quick access to container logs, lets you get a shell inside the container, and lets you easily manage container lifecycle (stop, remove, etc.).

To access the dashboard, follow the instructions for either Mac or Windows. If you open the dashboard now, you will see this tutorial running! The container name ( jolly_bouman below) is a randomly created name. So, you’ll most likely have a different name.

What is a container?

Now that you’ve run a container, what is a container? Simply put, a container is simply another process on your machine that has been isolated from all other processes on the host machine. That isolation leverages kernel namespaces and cgroups, features that have been in Linux for a long time. Docker has worked to make these capabilities approachable and easy to use.

Creating containers from scratch

If you’d like to see how containers are built from scratch, Liz Rice from Aqua Security has a fantastic talk in which she creates a container from scratch in Go. While she makes a simple container, this talk doesn’t go into networking, using images for the filesystem, and more. But, it gives a fantastic deep dive into how things are working.

What is a container image?

When running a container, it uses an isolated filesystem. This custom filesystem is provided by a container image. Since the image contains the container’s filesystem, it must contain everything needed to run an application — all dependencies, configuration, scripts, binaries, etc. The image also contains other configuration for the container, such as environment variables, a default command to run, and other metadata.

We’ll dive deeper into images later on, covering topics such as layering, best practices, and more.

If you’re familiar with chroot , think of a container as an extended version of chroot . The filesystem is simply coming from the image. But, a container adds additional isolation not available when simply using chroot.

CLI references

Refer to the following topics for further documentation on all CLI commands used in this article:

Install Docker Desktop on Windows

Estimated reading time: 6 minutes

Welcome to Docker Desktop for Windows. This page contains information about Docker Desktop for Windows system requirements, download URL, installation instructions, and automatic updates.

By downloading Docker Desktop, you agree to the terms of the Docker Software End User License Agreement and the Docker Data Processing Agreement.

System requirements

Your Windows machine must meet the following requirements to successfully install Docker Desktop.

WSL 2 backend

• Windows 10 64-bit: Home, Pro, Enterprise, or Education, version 1903 (Build 18362 or higher).
• Enable the WSL 2 feature on Windows. For detailed instructions, refer to the Microsoft documentation.

The following hardware prerequisites are required to successfully run WSL 2 on Windows 10:

• 64-bit processor with Second Level Address Translation (SLAT)
• 4GB system RAM
• 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.

Hyper-V backend and Windows containers

Windows 10 64-bit: Pro, Enterprise, or Education (Build 17134 or higher).

The following hardware prerequisites are required to successfully run Client Hyper-V on Windows 10:

• 64 bit processor with Second Level Address Translation (SLAT)
• 4GB system RAM
• BIOS-level hardware virtualization support must be enabled in the BIOS settings. For more information, see Virtualization.

Docker supports Docker Desktop on Windows for those versions of Windows 10 that are still within Microsoft’s servicing timeline.

What’s included in the installer

The Docker Desktop installation includes Docker Engine, Docker CLI client, Docker Compose, Notary, Kubernetes, and Credential Helper.

Containers and images created with Docker Desktop are shared between all user accounts on machines where it is installed. This is because all Windows accounts use the same VM to build and run containers. Note that it is not possible to share containers and images between user accounts when using the Docker Desktop WSL 2 backend.

Nested virtualization scenarios, such as running Docker Desktop on a VMWare or Parallels instance might work, but there are no guarantees. For more information, see Running Docker Desktop in nested virtualization scenarios.

About Windows containers

Looking for information on using Windows containers?

• Switch between Windows and Linux containers describes how you can toggle between Linux and Windows containers in Docker Desktop and points you to the tutorial mentioned above.
• Getting Started with Windows Containers (Lab) provides a tutorial on how to set up and run Windows containers on Windows 10, Windows Server 2016 and Windows Server 2019. It shows you how to use a MusicStore application with Windows containers.
• Docker Container Platform for Windows articles and blog posts on the Docker website.

Install Docker Desktop on Windows

Double-click Docker Desktop Installer.exe to run the installer.

If you haven’t already downloaded the installer ( Docker Desktop Installer.exe ), you can get it from Docker Hub. It typically downloads to your Downloads folder, or you can run it from the recent downloads bar at the bottom of your web browser.

When prompted, ensure the Enable Hyper-V Windows Features or the Install required Windows components for WSL 2 option is selected on the Configuration page.

Follow the instructions on the installation wizard to authorize the installer and proceed with the install.

When the installation is successful, click Close to complete the installation process.

If your admin account is different to 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.

Start Docker Desktop

Docker Desktop does not start automatically after installation. To start Docker Desktop, search for Docker, and select Docker Desktop in the search results.

When the whale icon in the status bar stays steady, Docker Desktop is up-and-running, and is accessible from any terminal window.

If the whale icon is hidden in the Notifications area, click the up arrow on the taskbar to show it. To learn more, see Docker Settings.

When the initialization is complete, Docker Desktop launches the onboarding tutorial. 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.

Congratulations! You are now successfully running Docker Desktop on Windows.

If you would like to rerun the tutorial, go to the Docker Desktop menu and select Learn.

Automatic updates

Starting with Docker Desktop 3.0.0, updates to Docker Desktop will be available automatically as delta updates from the previous version.

When an update is available, Docker Desktop displays an icon to indicate the availability of a newer version. Whenever convenient, you can start the download of the update in the background.

When the download finishes, all you need to do is to click Update and restart from the Docker menu. This installs the latest update and restarts Docker Desktop for the changes to take effect.

Uninstall Docker Desktop

To uninstall Docker Desktop from your Windows machine:

1. From the Windows Start menu, select Settings >Apps >Apps & features.
2. Select Docker Desktop from the Apps & features list and then select Uninstall.
3. Click Uninstall to confirm your selection.

Uninstalling Docker Desktop destroys Docker containers, images, volumes, and other Docker related data local to the machine, and removes the files generated by the application. Refer to the back up and restore data section to learn how to preserve important data before uninstalling.

Учебник. Начало работы с Docker Tutorial: Get started with Docker

В этом учебнике вы узнаете о создании и развертывании приложений Docker, включая использование нескольких контейнеров с базой данных и применение Docker Compose. In this tutorial, you’ll learn about creating and deploying Docker apps, including using multiple containers with a database, and using Docker Compose. Вы также развернете контейнерное приложение в Azure. You’ll also deploy your containerized app to Azure.

Начать изучение руководства Start the tutorial

Если вы уже запустили команду, чтобы приступить к работе с учебником, поздравляем! If you’ve already run the command to get started with the tutorial, congratulations! В противном случае откройте командную строку или окно Bash и выполните следующую команду: If not, open a command prompt or bash window, and run the command:

Обратите внимание на несколько используемых флагов. You’ll notice a few flags being used. Ниже приведены некоторые дополнительные сведения. Here’s some more info on them:

• -d — запуск контейнера в отключенном режиме (в фоновом окне) -d — run the container in detached mode (in the background)
• -p 80:80 — сопоставление порта 80 узла с портом 80 в контейнере. -p 80:80 — map port 80 of the host to port 80 in the container
• docker/getting-started — используемый образ. docker/getting-started — the image to use

Для сокращения полной команды можно использовать однозначные флаги. You can combine single character flags to shorten the full command. Например, приведенная выше команда может быть написана следующим образом: As an example, the command above could be written as:

Использование расширения VS Code The VS Code Extension

Прежде чем приступить к работе, необходимо выделить расширение Docker VS Code, которое позволяет быстро просмотреть контейнеры, работающие на вашем компьютере. Before going too far, we want to highlight the Docker VS Code Extension, which gives you a quick view of the containers running on your machine. Он обеспечивает быстрый доступ к журналам контейнеров, позволяет получить оболочку внутри контейнера и позволяет с легкостью управлять жизненным циклом контейнера (остановка, удаление и т. д.). It gives you quick access to container logs, lets you get a shell inside the container, and lets you easily manage container lifecycle (stop, remove, and so on).

Чтобы получить доступ к расширению, следуйте этим инструкциям. To access the extension, follow the instructions here. Используйте значок Docker слева, чтобы открыть представление Docker. Use the Docker icon on the left to open the Docker view. Если открыть расширение сейчас, вы увидите, что этот учебник работает. If you open the extension now, you will see this tutorial running! Имя контейнера ( angry_taussig ниже) является именем, созданным случайным образом. The container name ( angry_taussig below) is a randomly created name. Поэтому у вас, скорее всего, будет другое имя. So, you’ll most likely have a different name.

Что представляет собой контейнер? What is a container

Теперь, когда вы запустили контейнер, необходимо понять, что же такое контейнер? Now that you’ve run a container, what is a container? Проще говоря, контейнер — это просто другой процесс на компьютере, который был изолирован от всех других процессов на компьютере. Simply put, a container is simply another process on your machine that has been isolated from all other processes on the host machine. Такая изоляция использует пространства имен ядра и cgroups, компоненты, которые были в Linux в течение длительного времени. That isolation leverages kernel namespaces and cgroups, features that have been in Linux for a long time. Docker работал над тем, чтобы сделать эти возможности удобными и простыми в использовании. Docker has worked to make these capabilities approachable and easy to use.

Создание контейнеров с нуля. Если вы хотите увидеть, как создаются контейнеры с нуля, ознакомьтесь с видео, в котором Лиз Райс (Liz Rice) из компании Aqua Security создает контейнер с нуля в Go: Creating Containers from Scratch If you’d like to see how containers are built from scratch, Liz Rice from Aqua Security has a video in which she creates a container from scratch in Go:

Что представляет собой образ контейнера? What is a container image

При запуске контейнера используется изолированная файловая система. When running a container, it uses an isolated filesystem. Эта пользовательская файловая система предоставляется образом контейнера. This custom filesystem is provided by a container image. Поскольку образ содержит файловую систему контейнера, он должен содержать все необходимое для запуска приложения — все зависимости, конфигурацию, скрипты, двоичные файлы и т. д. Since the image contains the container’s filesystem, it must contain everything needed to run an application — all dependencies, configuration, scripts, binaries, and so on. Образ также содержит другую конфигурацию для контейнера, например переменные среды, команду, выполняемую по умолчанию, и другие метаданные. The image also contains other configuration for the container, such as environment variables, a default command to run, and other metadata.

В дальнейшем мы подробно рассмотрим образы, охватывающие такие темы, как слои, рекомендации и многое другое. We’ll dive deeper into images later on, covering topics such as layering, best practices, and more.

Если вы знакомы с chroot , рассмотрите контейнер как расширенную версию chroot . If you’re familiar with chroot , think of a container as an extended version of chroot . Файловая система просто берется из образа. The filesystem is simply coming from the image. Однако контейнер добавляет дополнительную изоляцию, которая недоступна при простом использовании chroot. But, a container adds additional isolation not available when simply using chroot.

Дальнейшие действия Next steps

Продолжайте изучать учебник. Continue with the tutorial!