Comment 3 for bug 1915280
Revision history for this message
| George Kraft (cynerva) wrote Re: docker login failed when relating to docker-registry with http-host configured | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Reproduction steps:
1. Deploy Charmed Kubernetes with docker instead of containerd
2. Deploy docker-registry as described in the docs[1]
3. Configure docker-registry with a bogus http-host e.g. https:/
4. Relate docker-registry to docker
5. Wait for docker to enter blocked/idle status with "docker login failed, see juju debug-log"
6. Configure docker-registry with http-host=
7. Wait for docker-registry and docker charms to run their hooks and enter idle state
At this point the docker charm should still show blocked/idle, even though it has logged in successfully.
[1]: https:/