mirror of https://github.com/docker/docs.git
ENGDOCS-1600-extensions (#18071)
* ENGDOCS-1600-extensions * ENGDOCS-1600-extensions * oauth image * resize images --------- Co-authored-by: Allie Sadler <alliesadler@f693mt7fh6.home>
This commit is contained in:
parent
a518247534
commit
93e4a87320
|
@ -13,7 +13,7 @@ Extensions can be composed of three (optional) components:
|
|||
- A backend: One or many containerised services running in the Docker Desktop VM
|
||||
- Executables: Shell scripts or binaries that Docker Desktop copies on the host when installing the extension
|
||||
|
||||

|
||||

|
||||
|
||||
An extension doesn't necessarily need to have all these components, but at least one of them depending on the extension features.
|
||||
To configure and run those components, Docker Desktop uses a `metadata.json` file. See the
|
||||
|
@ -79,7 +79,7 @@ or named pipe, depending on the operating system. If the backend was listening t
|
|||
prevent collision with other applications running on the host or in a container already. Also, some users are
|
||||
running Docker Desktop in constrained environments where they can't open ports on their machines.
|
||||
|
||||

|
||||

|
||||
|
||||
Finally, the backend can be built with any technology, as long as it can run in a container and listen on a socket.
|
||||
|
||||
|
@ -97,7 +97,7 @@ the users' machine.
|
|||
When Docker Desktop installs the extension, it copies the executables on the host as defined by the `host` section in
|
||||
the `metadata.json`. See the [ui metadata section](./metadata.md#host-section) for more details.
|
||||
|
||||

|
||||

|
||||
|
||||
However, since they're executed on the users' machine, they have to be available to the platform they're running on.
|
||||
For example, if you want to ship the `kubectl` executable, you need to provide a different version for Windows, Mac,
|
||||
|
|
Binary file not shown.
After Width: | Height: | Size: 74 KiB |
Binary file not shown.
After Width: | Height: | Size: 24 KiB |
Binary file not shown.
After Width: | Height: | Size: 104 KiB |
Binary file not shown.
After Width: | Height: | Size: 232 KiB |
|
@ -20,7 +20,7 @@ The Authorization Code grant type is used by confidential and public clients to
|
|||
|
||||
After the user returns to the client via the redirect URL, the application gets the authorization code from the URL and uses it to request an access token.
|
||||
|
||||

|
||||

|
||||
|
||||
The image above shows that:
|
||||
|
||||
|
|
Loading…
Reference in New Issue