Clarify instantly that Docker Desktop for Linux uses its own context (#16105)

* Clarify Docker Desktop for Linux custom context

Clarifying immediately that Docker Desktop for Linux has its own context would greatly improve the documentation and prevent further misunderstandings regarding allegedly missing images and containers, as well as problems regarding apps that use the default docker socket for communication (e.g. PhpStorm).

* Fix

Co-authored-by: Allie Sadler <102604716+aevesdocker@users.noreply.github.com>
This commit is contained in:
goulashsoup 2022-11-07 15:31:00 +01:00 committed by GitHub
parent a9b0774946
commit 8bf3c39cd6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 0 deletions

View File

@ -11,6 +11,15 @@ redirect_from:
> employees OR more than $10 million USD in annual revenue) requires a paid
> subscription.
>Important
>
>Docker Desktop on Linux runs a Virtual Machine (VM) so creates and uses a custom docker context `desktop-linux` on startup.
>
>This means images and containers deployed on the Linux Docker Engine (before installation) are not available in Docker Desktop for Linux.
>
>For more information see [What is the difference between Docker Desktop for Linux and Docker Engine](../faqs/linuxfaqs.md#what-is-the-difference-between-docker-desktop-for-linux-and-docker-engine).
{: .important}
This page contains information about general system requirements, supported platforms, and instructions on how to install Docker Desktop for Linux.
## System requirements