Learning Center
The Learning Center helps you get started with quick in-app walkthroughs and other resources for learning about Docker.
To access the Learning Center, select the
Learning Center
tab in Docker
Desktop.
For a more detailed guide about getting started, see
Get started
.
Sign in to Docker Desktop
Docker recommends that you authenticate using the
Sign in
option in the top-right corner of the Docker Dashboard.
Once logged in, you can access your Docker Hub repositories directly from Docker Desktop.
Authenticated users get a higher pull rate limit compared to anonymous users. For example, if you are authenticated, you get 200 pulls per 6 hour period, compared to 100 pulls per 6 hour period per IP address for anonymous users. For more information, see
Download rate limit
.
In large enterprises where admin access is restricted, administrators can
Configure registry.json to enforce sign-in
. Enforcing developers to authenticate through Docker Desktop also allows administrators to improve their organization’s security posture for containerized development by taking advantage of
Hardened Desktop
.
Credentials management for Linux users
Docker Desktop relies on
pass
to store credentials in gpg2-encrypted files.
Before signing in to Docker Hub from the Docker Dashboard or the Docker menu, you must initialize
pass
.
Docker Desktop displays a warning if you’ve not initialized
pass
.
You can initialize pass by using a gpg key. To generate a gpg key, run:
$ gpg --generate-key
The following is an example similar to what you see once you run the previous command:
GnuPG needs to construct a user ID to identify your key.
Real name: Molly
Email address: molly@example.com
You selected this USER-ID:
"Molly <molly@example.com>"
Change (N)ame, (E)mail, or (O)kay/(Q)uit? O
pub rsa3072 2022-03-31 [SC] [expires: 2024-03-30]
<generated gpg-id public key>
uid Molly <molly@example.com>
sub rsa3072 2022-03-31 [E] [expires: 2024-03-30]
To initialize pass, run the following command using the public key generated from the previous command:
$ pass init <generated gpg-id public key>
The following is an example similar to what you see once you run the previous command:
mkdir: created directory '/home/molly/.password-store/'
Password store initialized for <generated gpg-id public key>
Once you initialize pass, you can sign in on the Docker Dashboard and pull your private images.
When Docker CLI or Docker Desktop use credentials, a user prompt may pop up for the password you set during the gpg key generation.
