Private Docker Registry | Ralph A. Navarro Jr.Assess state of our registry- Our private docker registry is 2 years old.
- The container (named registry) is running on server a13.
- The registry is configured to respond to HTTP requests and not HTTPS.
- Our registry is not available from the public Internet due to security concerns.
Upgrade our registry- Backup our repositories (Only one; an older Xubuntu 16.04 image)
- Upgrade to the latest docker registry v2.7.1 image.
- Delete the container registry
- Rebuild registry container from new registry v2.7.1 image
- Copy the repository into the new registry container
- Until HTTPS is configured, a local (to this subnet) docker client must be configured to accept insecure docker connections.
- Verify that my laptop docker client can pull the repository from the newly upgraded private docker registry.
|
|
2 Comments
Candy O'Sullivan (Sutherland)
#new feature added: mobile access :-)
Candy O'Sullivan (Sutherland)
i.e. Confluence mobile enabled