mirror of https://github.com/docker/docs.git
Merge pull request #14164 from docker/master
Publish updates from master
This commit is contained in:
Usha Mandya
GitHub
commit
c06887642b
|
|
@ -0,0 +1,142 @@
|
|||
---
|
||||
description: Docker Desktop for Linux Tech Preview
|
||||
keywords: docker, linux, tech preview
|
||||
title: Docker Desktop for Linux (Tech Preview)
|
||||
toc_min: 1
|
||||
toc_max: 2
|
||||
---
|
||||
|
||||
Welcome to the Docker Desktop for Linux Tech Preview. This Tech Preview is aimed at early adopters who would like to try an experimental build of Docker Desktop for Linux and provide feedback.
|
||||
|
||||
Docker Desktop is an easy-to-install application that enables you to build and
|
||||
share containerized applications and microservices. Docker Desktop for Linux
|
||||
(DD4L) is the second-most popular feature request in our [public
|
||||
roadmap](https://github.com/docker/roadmap/projects/1){: target="_blank"
|
||||
rel="noopener" class="_"}.
|
||||
|
||||
## Download and install
|
||||
|
||||
Docker Desktop for Linux is currently available on Ubuntu 21.04, 21.10 and
|
||||
Debian distributions.
|
||||
|
||||
To install Docker Desktop for Linux:
|
||||
|
||||
1. Set up the [Docker repository](../../engine/install/ubuntu.md#install-using-the-repository).
|
||||
2. Download and install the Tech Preview Debian package:
|
||||
|
||||
```console
|
||||
$ curl https://desktop-stage.docker.com/linux/main/amd64/73701/docker-desktop.deb --output docker-desktop.deb
|
||||
$ sudo apt install ./docker-desktop.deb
|
||||
```
|
||||
|
||||
## Check the shared memory
|
||||
|
||||
Before you run Docker Desktop for Linux, verify whether the shared memory available on the host is higher than the memory allocated to the VM. By default, Docker Desktop allocates half of the memory and CPU from the host.
|
||||
|
||||
```console
|
||||
$ df -h /dev/shm
|
||||
Filesystem Size Used Avail Use% Mounted on
|
||||
tmpfs 16G 200M 16G 2% /dev/shm
|
||||
```
|
||||
|
||||
To set the shared memory size, run:
|
||||
|
||||
```console
|
||||
$ sudo mount -o remount,size=<the-size-you-want-in-GB> /dev/shm
|
||||
```
|
||||
|
||||
To ensure this setting persists after a reboot, add the following entry to the `/etc/fstab`:
|
||||
|
||||
```console
|
||||
none /dev/shm tmpfs defaults,size=<the-size-you-want-in-GB> 0 0
|
||||
```
|
||||
|
||||
For example:
|
||||
|
||||
```console
|
||||
none /dev/shm tmpfs defaults,size=8G 0 0
|
||||
```
|
||||
|
||||
## Launch Docker Desktop
|
||||
|
||||
To start Docker Desktop for Linux, search **Docker Desktop** on the
|
||||
**Applications** menu and open it. This launches the whale menu icon and opens
|
||||
the Docker Dashboard, reporting the status of Docker Desktop.
|
||||
|
||||
Alternatively, open a terminal and run:
|
||||
|
||||
```console
|
||||
$ systemctl --user start docker-desktop
|
||||
```
|
||||
|
||||
When Docker Desktop starts, it creates a dedicated context that the Docker CLI can use as a target. This is to avoid a clash with a local Docker Engine that may be running on the Linux host and using the default context.
|
||||
|
||||
Run the following command to switch to the desktop-linux context.
|
||||
|
||||
```console
|
||||
$ docker context use desktop-linux
|
||||
```
|
||||
|
||||
The Docker Desktop installer updates Docker Compose and the Docker CLI binaries
|
||||
on the host. It installs Docker Compose V2 as the default Docker Compose. It
|
||||
also replaces the default Docker CLI with a new Docker CLI binary that includes
|
||||
cloud-integration capabilities.
|
||||
|
||||
After you’ve successfully installed Docker Desktop, you can check the versions
|
||||
of these binaries by running the following command:
|
||||
|
||||
```console
|
||||
$ docker-compose version
|
||||
Docker Compose version v2.2.3
|
||||
|
||||
$ docker --version
|
||||
Docker version 20.10.12, build e91ed57
|
||||
|
||||
$ docker version
|
||||
Client: Docker Engine - Community
|
||||
Cloud integration: 1.0.17
|
||||
Version: 20.10.12
|
||||
API version: 1.41
|
||||
...
|
||||
```
|
||||
|
||||
To enable Docker Desktop to start on login, from the Docker menu, select
|
||||
**Settings** > **General** > **Start Docker Desktop when you log in**.
|
||||
|
||||
Alternatively, open a terminal and run:
|
||||
|
||||
```console
|
||||
$ systemctl --user enable docker-desktop
|
||||
```
|
||||
|
||||
To stop Docker Desktop, click on the whale menu tray icon to open the Docker menu and select **Quit Docker Desktop**.
|
||||
|
||||
Alternatively, open a terminal and run:
|
||||
|
||||
```console
|
||||
$ systemctl --user stop docker-desktop
|
||||
```
|
||||
|
||||
## Logs
|
||||
|
||||
If you experience any issues, you can access Docker Desktop logs by running the following command:
|
||||
|
||||
```console
|
||||
$ journalctl --user --unit=docker-desktop
|
||||
```
|
||||
|
||||
You can also find additional logs for the internal components included in Docker
|
||||
Desktop at `$HOME/.docker/desktop/log/`.
|
||||
|
||||
## Uninstall
|
||||
|
||||
To remove Docker Desktop for Linux, run:
|
||||
|
||||
```console
|
||||
$ sudo apt remove docker-desktop
|
||||
```
|
||||
|
||||
## Feedback
|
||||
|
||||
Your feedback is important to us. Let us know what you think by adding a comment
|
||||
on our [Docker for Linux public roadmap](https://github.com/docker/roadmap/issues/39){: target="_blank" rel="noopener" class="_"} issue.
|
||||
|
|
@ -195,19 +195,24 @@ $ docker build --no-cache --progress=plain --secret id=mysecret,src=mysecret.txt
|
|||
> Please see [Build secrets and SSH forwarding in Docker 18.09](https://medium.com/@tonistiigi/build-secrets-and-ssh-forwarding-in-docker-18-09-ae8161d066)
|
||||
> for more information and examples.
|
||||
|
||||
The `docker build` has a `--ssh` option to allow the Docker Engine to forward
|
||||
SSH agent connections. For more information on SSH agent, see the
|
||||
[OpenSSH man page](https://man.openbsd.org/ssh-agent).
|
||||
Some commands in a `Dockerfile` may need specific SSH authentication - for example, to clone a private repository.
|
||||
Rather than copying private keys into the image, which runs the risk of exposing them publicly, `docker build` provides a way to use the host system's ssh access while building the image.
|
||||
|
||||
Only the commands in the `Dockerfile` that have explicitly requested the SSH
|
||||
access by defining `type=ssh` mount have access to SSH agent connections. The
|
||||
other commands have no knowledge of any SSH agent being available.
|
||||
There are three steps to this process.
|
||||
|
||||
To request SSH access for a `RUN` command in the `Dockerfile`, define a mount
|
||||
with type `ssh`. This will set up the `SSH_AUTH_SOCK` environment variable to
|
||||
make programs relying on SSH automatically use that socket.
|
||||
First, run `ssh-add` to add private key identities to the authentication agent.
|
||||
If you have more than one SSH key and your default `id_rsa` is not the one you use for accessing the resources in question, you'll need to add that key by path: `ssh-add ~/.ssh/<some other key>`.
|
||||
(For more information on SSH agent, see the [OpenSSH man page](https://man.openbsd.org/ssh-agent).)
|
||||
|
||||
Here is an example Dockerfile using SSH in the container:
|
||||
Second, when running `docker build`, use the `--ssh` option to pass in an existing SSH agent connection socket.
|
||||
For example, `--ssh default=$SSH_AUTH_SOCK`, or the shorter equivalent, `--ssh default`.
|
||||
|
||||
Third, to make use of that SSH access in a `RUN` command in the `Dockerfile`, define a mount with type `ssh`.
|
||||
This will set the `SSH_AUTH_SOCK` environment variable for that command to the value provided by the host to `docker build`, which will cause any programs in the `RUN` command which rely on SSH to automatically use that socket.
|
||||
Only the commands in the `Dockerfile` that have explicitly requested SSH access by defining `type=ssh` mount will have access to SSH agent connections.
|
||||
The other commands have will no knowledge of any SSH agent being available.
|
||||
|
||||
Here is an example `Dockerfile` using SSH in the container:
|
||||
|
||||
```dockerfile
|
||||
# syntax=docker/dockerfile:1
|
||||
|
|
@ -223,14 +228,16 @@ RUN mkdir -p -m 0600 ~/.ssh && ssh-keyscan github.com >> ~/.ssh/known_hosts
|
|||
RUN --mount=type=ssh git clone git@github.com:myorg/myproject.git myproject
|
||||
```
|
||||
|
||||
Once the `Dockerfile` is created, use the `--ssh` option for connectivity with
|
||||
the SSH agent.
|
||||
The image could be built as follows:
|
||||
|
||||
```console
|
||||
$ docker build --ssh default .
|
||||
```
|
||||
|
||||
You may need to run `ssh-add` to add private key identities to the authentication agent first for this to work.
|
||||
As with `--mount=type=secret`, you can specify an `id` if you want to use multiple sockets per build and want to differentiate them.
|
||||
For example, you could run `docker build --ssh main=$SSH_AUTH_SOCK --ssh other=$OTHER_SSH_AUTH_SOCK`.
|
||||
In your `Dockerfile`, you could then have a `RUN --mount=type=ssh,id=main` and a `RUN --mount=type=ssh,id=other` to use those two sockets.
|
||||
If a `--mount=type=ssh` doesn't specify an `id`, `default` is assumed.
|
||||
|
||||
## Troubleshooting : issues with private registries
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue