Clearified pass initialization flow (#16276)

to prevent confusion like the one discussed in [this issue](https://github.com/docker/desktop-linux/issues/85)
This commit is contained in:
Tom 2022-12-05 10:40:10 +02:00 committed by GitHub
parent 4de75afb97
commit d7136d0348
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 5 deletions

View File

@ -82,17 +82,17 @@ You selected this USER-ID:
Change (N)ame, (E)mail, or (O)kay/(Q)uit? O
...
pub rsa3072 2022-03-31 [SC] [expires: 2024-03-30]
7865BA9185AFA2C26C5B505669FC4F36530097C2
<generated gpg-id public key>
uid Molly <molly@example.com>
sub rsa3072 2022-03-31 [E] [expires: 2024-03-30]
```
To initialize `pass`, run:
To initialize `pass`, run the following command using the public key generated from the previous command
```console
molly@ubuntu:~$ pass init 7865BA9185AFA2C26C5B505669FC4F36530097C2
molly@ubuntu:~$ pass init <generated gpg-id public key>
mkdir: created directory '/home/molly/.password-store/'
Password store initialized for 7865BA9185AFA2C26C5B505669FC4F36530097C2
Password store initialized for <generated gpg-id public key>
```
Once `pass` is initialized, you can sign in on the Docker Dashboard and pull your private images.
@ -111,4 +111,4 @@ docker.io/molly/privateimage:latest
- [Explore Docker Desktop](use-desktop/index.md) and its features.
- Change your Docker Desktop settings
- [Browse common FAQs](faqs/general.md)
- [Browse common FAQs](faqs/general.md)