Comment 11 for bug 1906372

What's interesting is that there's now 2 external services affected, called by 2 separate clients:

1. charm store (used by the juju client)
2. rocks (used by k8s itself, ie containerd)

Given containerd is also affected, ie it connects to rocks to pull an image totally outside of juju, this doesn't look like a Juju issue per se, and really does appear to be an artifact of the deployment environment.