mirror of https://github.com/docker/docs.git
190 lines
8.7 KiB
Markdown
190 lines
8.7 KiB
Markdown
---
|
|
title: "Orientation and setup"
|
|
keywords: get started, setup, orientation, quickstart, intro, concepts, containers, docker desktop
|
|
description: Get oriented on some basics of Docker and install Docker Desktop.
|
|
redirect_from:
|
|
- /engine/getstarted-voting-app/
|
|
- /engine/getstarted-voting-app/cleanup/
|
|
- /engine/getstarted-voting-app/create-swarm/
|
|
- /engine/getstarted-voting-app/customize-app/
|
|
- /engine/getstarted-voting-app/deploy-app/
|
|
- /engine/getstarted-voting-app/node-setup/
|
|
- /engine/getstarted-voting-app/test-drive/
|
|
- /engine/getstarted/
|
|
- /engine/getstarted/last_page/
|
|
- /engine/getstarted/step_five/
|
|
- /engine/getstarted/step_four/
|
|
- /engine/getstarted/step_one/
|
|
- /engine/getstarted/step_six/
|
|
- /engine/getstarted/step_three/
|
|
- /engine/getstarted/step_two/
|
|
- /engine/quickstart/
|
|
- /engine/tutorials/
|
|
- /engine/tutorials/dockerimages/
|
|
- /engine/tutorials/dockerizing/
|
|
- /engine/tutorials/usingdocker/
|
|
- /engine/userguide/containers/dockerimages/
|
|
- /engine/userguide/dockerimages/
|
|
- /engine/userguide/intro/
|
|
- /get-started/part1/
|
|
- /get-started/part5/
|
|
- /get-started/part6/
|
|
- /getstarted/
|
|
- /getting-started/
|
|
- /learn/
|
|
- /linux/last_page/
|
|
- /linux/started/
|
|
- /linux/step_four/
|
|
- /linux/step_one/
|
|
- /linux/step_six/
|
|
- /linux/step_three/
|
|
- /linux/step_two/
|
|
- /mac/last_page/
|
|
- /mac/started/
|
|
- /mac/step_four/
|
|
- /mac/step_one/
|
|
- /mac/step_six/
|
|
- /mac/step_three/
|
|
- /mac/step_two/
|
|
- /userguide/dockerimages/
|
|
- /userguide/dockerrepos/
|
|
- /windows/last_page/
|
|
- /windows/started/
|
|
- /windows/step_four/
|
|
- /windows/step_one/
|
|
- /windows/step_six/
|
|
- /windows/step_three/
|
|
- /windows/step_two/
|
|
---
|
|
|
|
> **Update to the Docker Desktop terms**
|
|
>
|
|
> 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.
|
|
{: .important}
|
|
|
|
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
|
|
- Run 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](../language/index.md).
|
|
|
|
We also recommend the video workshop from DockerCon 2022. Watch the video below or use the links to open the video at a particular section.
|
|
|
|
* [Docker overview and installation](https://youtu.be/gAGEar5HQoU)
|
|
* [Pull, run, and explore containers](https://youtu.be/gAGEar5HQoU?t=1400)
|
|
* [Build a container image](https://youtu.be/gAGEar5HQoU?t=3185)
|
|
* [Containerize an app](https://youtu.be/gAGEar5HQoU?t=4683)
|
|
* [Connect a DB and set up a bind mount](https://youtu.be/gAGEar5HQoU?t=6305)
|
|
* [Deploy a container to the cloud](https://youtu.be/gAGEar5HQoU?t=8280)
|
|
|
|
<iframe src="https://www.youtube-nocookie.com/embed/gAGEar5HQoU" style="max-width: 100%; aspect-ratio: 16 / 9;" width="560" height="auto" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
|
|
|
|
## 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:
|
|
|
|
[Mac with Intel chip](https://desktop.docker.com/mac/main/amd64/Docker.dmg?utm_source=docker&utm_medium=webreferral&utm_campaign=docs-driven-download-mac-amd64){: .button .primary-btn }
|
|
[Mac with Apple chip](https://desktop.docker.com/mac/main/arm64/Docker.dmg?utm_source=docker&utm_medium=webreferral&utm_campaign=docs-driven-download-mac-arm64){: .button .primary-btn }
|
|
[Windows](https://desktop.docker.com/win/main/amd64/Docker%20Desktop%20Installer.exe?utm_source=docker&utm_medium=webreferral&utm_campaign=docs-driven-download-win-amd64){: .button .primary-btn }
|
|
[Linux](../desktop/install/linux-install.md){: .button .primary-btn}
|
|
|
|
For Docker Desktop installation instructions, see:
|
|
- [Install Docker Desktop on Mac](../desktop/install/mac-install.md)
|
|
- [Install Docker Desktop on Windows](../desktop/install/windows-install.md)
|
|
- [Install Docker Desktop on Linux](../desktop/install/linux-install.md)
|
|
|
|
## 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:
|
|
|
|
```console
|
|
$ docker run -d -p 80:80 docker/getting-started
|
|
```
|
|
|
|
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. To access the tutorial, open a web browser and navigate to `http://localhost:80`. If you already have a service listening on port 80 on your host machine, you can specify another port. For example, specify `-p 3000:80` and then access the tutorial via a web browser at `http://localhost:3000`.
|
|
- `docker/getting-started` - Specify the image to use.
|
|
|
|
> **Tip**
|
|
>
|
|
> You can combine single character flags to shorten the full command.
|
|
> As an example, the command above could be written as:
|
|
>
|
|
> ```console
|
|
> $ docker run -dp 80:80 docker/getting-started
|
|
> ```
|
|
|
|
## 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, Windows, and Linux.
|
|
It gives you quick access to container logs, lets you get a shell inside the container, and lets you
|
|
easily manage container lifecycles (stop, remove, etc.).
|
|
|
|
To access the dashboard, follow the instructions in the
|
|
[Docker Desktop manual](../desktop/index.md). 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
|
|
a sandboxed process on your machine that is isolated from all other processes
|
|
on the host machine. That isolation leverages [kernel namespaces and cgroups](https://medium.com/@saschagrunert/demystifying-containers-part-i-kernel-space-2c53d6979504),
|
|
features that have been in Linux for a long time. Docker has worked to make these
|
|
capabilities approachable and easy to use. To summarize, a container:
|
|
|
|
- is a runnable instance of an image. You can create, start, stop, move, or delete a container using the DockerAPI or CLI.
|
|
- can be run on local machines, virtual machines or deployed to the cloud.
|
|
- is portable (can be run on any OS).
|
|
- is isolated from other containers and runs its own software, binaries, and configurations.
|
|
|
|
> **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 the talk
|
|
> does not go into networking, using images for the filesystem, and other advanced topics,
|
|
> it gives a _fantastic_ deep dive into how things are working.
|
|
>
|
|
> <iframe src="https://www.youtube-nocookie.com/embed/8fi7uSYlOdc" style="max-width: 100%; aspect-ratio: 16 / 9;" width="560" height="auto" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
|
|
|
|
## 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, configurations, 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.
|
|
|
|
> **Info**
|
|
>
|
|
> 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:
|
|
|
|
- [docker version](../engine/reference/commandline/version.md)
|
|
- [docker run](../engine/reference/commandline/run.md)
|
|
- [docker image](../engine/reference/commandline/image.md)
|
|
- [docker container](../engine/reference/commandline/container.md)
|
|
|