Docker system requirements linux

Install Docker Engine from binaries

Estimated reading time: 5 minutes

Note: You may have been redirected to this page because there is no longer a dynamically-linked Docker package for your Linux distribution.

If you want to try Docker or use it in a testing environment, but you’re not on a supported platform, you can try installing from static binaries. If possible, you should use packages built for your operating system, and use your operating system’s package management system to manage Docker installation and upgrades. Be aware that 32-bit static binary archives do not include the Docker daemon.

Static binaries for the Docker daemon binary are only available for Linux (as dockerd ). Static binaries for the Docker client are available for Linux and macOS (as docker ).

This topic discusses binary installation for both Linux and macOS:

Install daemon and client binaries on Linux

Prerequisites

Before attempting to install Docker from binaries, be sure your host machine meets the prerequisites:

• A 64-bit installation
• Version 3.10 or higher of the Linux kernel. The latest version of the kernel available for your platform is recommended.
• iptables version 1.4 or higher
• git version 1.7 or higher
• A ps executable, usually provided by procps or a similar package.
• XZ Utils 4.9 or higher
• A properly mounted cgroupfs hierarchy; a single, all-encompassing cgroup mount point is not sufficient. See Github issues #2683, #3485, #4568).

Secure your environment as much as possible

OS considerations

Enable SELinux or AppArmor if possible.

It is recommended to use AppArmor or SELinux if your Linux distribution supports either of the two. This helps improve security and blocks certain types of exploits. Review the documentation for your Linux distribution for instructions for enabling and configuring AppArmor or SELinux.

If either of the security mechanisms is enabled, do not disable it as a work-around to make Docker or its containers run. Instead, configure it correctly to fix any problems.

Docker daemon considerations

Enable seccomp security profiles if possible. See Enabling seccomp for Docker.

Enable user namespaces if possible. See the Daemon user namespace options.

Install static binaries

Download the static binary archive. Go to https://download.docker.com/linux/static/stable/ (or change stable to nightly or test ), choose your hardware platform, and download the .tgz file relating to the version of Docker Engine you want to install.

Extract the archive using the tar utility. The dockerd and docker binaries are extracted.

Optional: Move the binaries to a directory on your executable path, such as /usr/bin/ . If you skip this step, you must provide the path to the executable when you invoke docker or dockerd commands.

Start the Docker daemon:

If you need to start the daemon with additional options, modify the above command accordingly or create and edit the file /etc/docker/daemon.json to add the custom configuration options.

Verify that Docker is installed correctly by running the hello-world image.

This command downloads a test image and runs it in a container. When the container runs, it prints a message and exits.

Install client binaries on macOS

The macOS binary includes the Docker client only. It does not include the dockerd daemon.

Download the static binary archive. Go to https://download.docker.com/mac/static/stable/x86_64/, (or change stable to nightly or test ), and download the .tgz file relating to the version of Docker Engine you want to install.

Extract the archive using the tar utility. The docker binary is extracted.

Clear the extended attributes to allow it run.

In case executing docker/docker you get the error message: ‘docker’ is damaged and cannot be opened. You should move it to the bin.

Apple takes care about our security. Hence, we need to remove the security mechanism preventing us running the executable.

Now, when you run the following command, you can see the Docker CLI usage instructions:

Optional: Move the binary to a directory on your executable path, such as /usr/local/bin/ . If you skip this step, you must provide the path to the executable when you invoke docker or dockerd commands.

Verify that Docker is installed correctly by running the hello-world image. The value of is a hostname or IP address running the Docker daemon and accessible to the client.

This command downloads a test image and runs it in a container. When the container runs, it prints a message and exits.

Источник

Install Docker Engine

Estimated reading time: 6 minutes

Supported platforms

Docker Engine is available on a variety of Linux platforms, macOS and Windows 10 through Docker Desktop, and as a static binary installation. Find your preferred operating system below.

Desktop

Platform	x86_64 / amd64	arm64 (Apple Silicon)
Docker Desktop for Mac (macOS)
Docker Desktop for Windows		В

Server

Docker provides .deb and .rpm packages from the following Linux distributions and architectures:

Platform	x86_64 / amd64	arm64 / aarch64	arm (32-bit)	s390x
CentOS			В	В
Debian				В
Fedora			В	В
Raspbian	В	В		В
RHEL	В	В	В
SLES	В	В	В
Ubuntu
Binaries				В

Other Linux distributions

While the instructions below may work, Docker does not test or verify installation on derivatives.

• Users of Debian derivatives such as “BunsenLabs Linux”, “Kali Linux” or “LMDE” (Debian-based Mint) should follow the installation instructions for Debian, substituting the version of their distro for the corresponding Debian release. Refer to the documentation of your distro to find which Debian release corresponds with your derivative version.
• Likewise, users of Ubuntu derivatives such as “Kubuntu”, “Lubuntu” or “Xubuntu” should follow the installation instructions for Ubuntu, substituting the version of their distro for the corresponding Ubuntu release. Refer to the documentation of your distro to find which Ubuntu release corresponds with your derivative version.
• Some Linux distributions are providing a package of Docker Engine through their package repositories. These packages are built and maintained by the Linux distribution’s package maintainers and may have differences in configuration or built from modified source code. Docker is not involved in releasing these packages and bugs or issues involving these packages should be reported in your Linux distribution’s issue tracker.

Docker provides binaries for manual installation of Docker Engine. These binaries are statically linked and can be used on any Linux distribution.

Release channels

Docker Engine has three types of update channels, stable, test, and nightly:

• The Stable channel gives you latest releases for general availability.
• The Test channel gives pre-releases that are ready for testing before general availability (GA).
• The Nightly channel gives you latest builds of work in progress for the next major release.

Stable

Year-month releases are made from a release branch diverged from the master branch. The branch is created with format . , for example 20.10 . The year-month name indicates the earliest possible calendar month to expect the release to be generally available. All further patch releases are performed from that branch. For example, once v20.10.0 is released, all subsequent patch releases are built from the 20.10 branch.

In preparation for a new year-month release, a branch is created from the master branch with format YY.mm when the milestones desired by Docker for the release have achieved feature-complete. Pre-releases such as betas and release candidates are conducted from their respective release branches. Patch releases and the corresponding pre-releases are performed from within the corresponding release branch.

Nightly

Nightly builds give you the latest builds of work in progress for the next major release. They are created once per day from the master branch with the version format:

where the time is the commit time in UTC and the final suffix is the prefix of the commit hash, for example 0.0.0-20180720214833-f61e0f7 .

These builds allow for testing from the latest code on the master branch. No qualifications or guarantees are made for the nightly builds.

Support

Docker Engine releases of a year-month branch are supported with patches as needed for one month after the next year-month general availability release.

This means bug reports and backports to release branches are assessed until the end-of-life date.

After the year-month branch has reached end-of-life, the branch may be deleted from the repository.

Backporting

Backports to the Docker products are prioritized by the Docker company. A Docker employee or repository maintainer will endeavour to ensure sensible bugfixes make it into active releases.

If there are important fixes that ought to be considered for backport to active release branches, be sure to highlight this in the PR description or by adding a comment to the PR.

Upgrade path

Patch releases are always backward compatible with its year-month version.

Licensing

Docker is licensed under the Apache License, Version 2.0. See LICENSE for the full license text.

Reporting security issues

The Docker maintainers take security seriously. If you discover a security issue, please bring it to their attention right away!

Please DO NOT file a public issue; instead send your report privately to security@docker.com.

Security reports are greatly appreciated, and Docker will publicly thank you for it.

Get started

After setting up Docker, you can learn the basics with Getting started with Docker.

Источник

Docker Desktop overview

Estimated reading time: 2 minutes

Update to the Docker Desktop terms

Professional use of Docker Desktop in large organizations (more than 250 employees or more than $10 million in revenue) requires users to have a paid Docker subscription. While the effective date of these terms is August 31, 2021, there is a grace period until January 31, 2022 for those that require a paid subscription. For more information, see Docker Desktop License Agreement.

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. Docker Desktop includes Docker Engine, Docker CLI client, Docker Compose, Docker Content Trust, Kubernetes, and Credential Helper.

Docker Desktop works with your choice of development tools and languages and gives you access to a vast library of certified images and templates in Docker Hub. This enables development teams to extend their environment to rapidly auto-build, continuously integrate, and collaborate using a secure repository.

Some of the key features of Docker Desktop include:

• 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

Docker Desktop is available for Mac and Windows. For download information, system requirements, and installation instructions, see:

For information about Docker Desktop licensing, see Docker Desktop License Agreement.

Configure Docker Desktop

To learn about the various UI options and their usage, see:

Release notes

For information about new features, improvements, and bug fixes in Docker Desktop releases, see:

Источник