Added example command for `docker context import` (#9423)

Added an actual `docker context import` command since the use of this command in conjunction with client bundles was not present in this or the `docker context` documentation. Also increased the emphasis of using `docker context import` vs. prior methods by pulling the new feature out of the note. This information is important and was not obvious enough in the note.
This commit is contained in:
Nathan Jones 2019-09-11 11:32:32 -04:00 committed by Olly P
parent f2f0dca20c
commit 17f66d0392
1 changed files with 13 additions and 4 deletions

View File

@ -85,10 +85,19 @@ and the `DOCKER_CERT_PATH` environment variable to use the client certificates
that are included in the client bundle you downloaded. The utility scripts also
run the `kubectl config` command to configure kubectl.
> **Note**: In Docker Enterprise 3.0, new files are contained in the UCP bundle. These changes support
the use of `.zip` files with `docker context import` and allow you to directly change your context
using the bundle `.zip` file. Refer to [Working with Contexts](/engine/context/working-with-contexts/)
for more information.
### Use client certificates with Docker contexts
In Docker Enterprise 3.0, new files are contained in the UCP bundle. These changes support
the use of `.zip` files with `docker context import` and allow you to directly change
your context using the bundle `.zip` file. Navigate to the directory where you downloaded
the user bundle and use `docker context import` to add the new context:
```bash
cd client-bundle && docker context import myucp ucp-bundle-$USER.zip"
```
> **Note**: Refer to [Working with Contexts](/engine/context/working-with-contexts/)
for more information on using Docker contexts.
To confirm that your client tools are now communicating with UCP, run: