Update the docs so that users don't use `echo` when creating secrets from STDIN. `echo` adds a trailing new line, so users will probably be confused when their passwords don't work. Signed-off-by: Joao Fernandes <joao.fernandes@docker.com>
2.4 KiB
2.4 KiB
title, description, keywords
title | description | keywords | |
---|---|---|---|
secret create | The secret create command description and usage |
|
secret create
Usage: docker secret create [OPTIONS] SECRET [file|-]
Create a secret from a file or STDIN as content
Options:
-l, --label list Secret labels
--template-driver string Template driver
Description
Creates a secret using standard input or from a file for the secret content. You must run this command on a manager node.
For detailed information about using secrets, refer to manage sensitive data with Docker secrets.
Examples
Create a secret
$ printf <secret> | docker secret create my_secret -
onakdyv307se2tl7nl20anokv
$ docker secret ls
ID NAME CREATED UPDATED
onakdyv307se2tl7nl20anokv my_secret 6 seconds ago 6 seconds ago
Create a secret with a file
$ docker secret create my_secret ./secret.json
dg426haahpi5ezmkkj5kyl3sn
$ docker secret ls
ID NAME CREATED UPDATED
dg426haahpi5ezmkkj5kyl3sn my_secret 7 seconds ago 7 seconds ago
Create a secret with labels
$ docker secret create --label env=dev \
--label rev=20170324 \
my_secret ./secret.json
eo7jnzguqgtpdah3cm5srfb97
$ docker secret inspect my_secret
[
{
"ID": "eo7jnzguqgtpdah3cm5srfb97",
"Version": {
"Index": 17
},
"CreatedAt": "2017-03-24T08:15:09.735271783Z",
"UpdatedAt": "2017-03-24T08:15:09.735271783Z",
"Spec": {
"Name": "my_secret",
"Labels": {
"env": "dev",
"rev": "20170324"
}
}
}
]