Context import update (#1136)

* Added info for .zip file import

* Note for UCP client bundle changes

* Wording updates

* Syntax fix
This commit is contained in:
paigehargrave 2019-06-06 16:06:47 -04:00 committed by GitHub
parent e15c48ae2d
commit 980a6fadb0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 7 additions and 0 deletions

View File

@ -85,6 +85,11 @@ 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 that are included in the client bundle you downloaded. The utility scripts also
run the `kubectl config` command to configure kubectl. 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.
To confirm that your client tools are now communicating with UCP, run: To confirm that your client tools are now communicating with UCP, run:
<ul class="nav nav-tabs"> <ul class="nav nav-tabs">

View File

@ -210,6 +210,8 @@ You can verify that the context was imported with `docker context ls`.
The format of the import command is `docker context import <context-name> <context-file>`. The format of the import command is `docker context import <context-name> <context-file>`.
> **Note**: You can import the client bundle `.zip` file generated from UCP and run a command to set your context to UCP. For example, `docker context import ctx-name ucp-bundle.zip`.
Now, let's look at exporting just the Kubernetes parts of a context. Now, let's look at exporting just the Kubernetes parts of a context.
### Exporting a Kubernetes context ### Exporting a Kubernetes context