Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 32 additions & 0 deletions content/manuals/desktop/setup/install/linux/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -205,6 +205,38 @@ Sign out and sign back in so that your group membership is re-evaluated.

Docker Desktop for Linux uses a per-user socket instead of the system-wide `/var/run/docker.sock`. Docker SDKs and tools that connect directly to the Docker daemon need the `DOCKER_HOST` environment variable set to connect to Docker Desktop. For configuration details, see [How do I use Docker SDKs with Docker Desktop for Linux?](/manuals/desktop/troubleshoot-and-support/faqs/linuxfaqs.md#how-do-i-use-docker-sdks-with-docker-desktop-for-linux).

## Verify your installation

After installing Docker Desktop, verify it is working correctly:

1. Open a terminal and check the Docker version:
```console
$ docker --version
```

You should see output similar to:
```text
Docker version 27.x.x, build xxxxxxx
```

1. Run the hello-world container to confirm Docker Desktop is working end-to-end:
```console
$ docker run hello-world
```

If successful, you should see:
```
Hello from Docker!
This message shows that your installation appears to be working correctly.
```

1. Check that Docker Desktop is using the correct context:
```console
$ docker context ls
```

The `desktop-linux` context should be marked with an asterisk (`*`) as the active context.

## Where to go next

- Install Docker Desktop for Linux for your specific Linux distribution:
Expand Down
11 changes: 11 additions & 0 deletions content/reference/compose-file/services.md
Original file line number Diff line number Diff line change
Expand Up @@ -1956,6 +1956,17 @@ secrets:

`security_opt` overrides the default labeling scheme for each container.

Options accept either `option=value` or `option:value` syntax. For boolean options
such as `no-new-privileges`, the value may be omitted entirely, in which case the
option is treated as enabled. The following syntaxes are all equivalent:

```yml
security_opt:
- no-new-privileges
- no-new-privileges=true
- no-new-privileges:true
```

```yml
security_opt:
- label=user:USER
Expand Down
Loading