Fix `docker secret` command documentation on ECS context

Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
This commit is contained in:
Nicolas De Loof 2021-01-18 09:57:16 +01:00
parent 89e422cb32
commit 88095576d7
No known key found for this signature in database
GPG Key ID: 9858809D6F8F6E7E
1 changed files with 12 additions and 1 deletions

View File

@ -196,8 +196,19 @@ The Docker Compose CLI automatically configures authorization so you can pull pr
For your convenience, the Docker Compose CLI offers the `docker secret` command, so you can manage secrets created on AWS SMS without having to install the AWS CLI.
First, create `token.json` file to define your DockerHub username and access token.
See [this document](https://docs.docker.com/docker-hub/access-tokens/) on generating managing access tokens:
```json
{
"username":"DockerHubUserName",
"password":"DockerHubAccessToken"
}
```
The you can create a secret from this file using `docker secret`:
```console
docker secret create dockerhubAccessToken --username <dockerhubuser> --password <dockerhubtoken>
docker secret create dockerhubAccessToken token.json
arn:aws:secretsmanager:eu-west-3:12345:secret:DockerHubAccessToken
```