Comment 5 for bug 1846551

Also reported here: https://bugs.launchpad.net/charm-containerd/+bug/1955658

I recommend working around this by setting the no_proxy config of the containerd charm. When the no_proxy config is set, the charm will ignore the juju-no-proxy model config, and it will *not* expand CIDRs. Assuming your juju-no-proxy looks like this:

localhost,127.0.0.1,::1,10.0.0.0/8

You can set no_proxy to this:

$ juju config containerd no_proxy="localhost,127.0.0.1,::1,10.0.0.0/8"

Containerd itself will ignore the 10.0.0.0/8 entry because it doesn't understand CIDRs. Including it can still be helpful since there are child processes, like Calico CNI, that will inherit the environment and can handle CIDRs.