Comment 6 for bug 1850862

This is marked fixed-released for containerd but I'm still seeing this behavior on the stable channel rev 64 on a new deploy.

containerd:
  charm: cs:~containers/containerd
  options:
      gpu_driver: none

The proxy is set in the juju model:
    juju-http-proxy: http://squid.internal:3128/
    juju-https-proxy: http://squid.internal:3128/
    apt-http-proxy: http://squid.internal:3128/
    apt-https-proxy: http://squid.internal:3128/
    snap-http-proxy: http://squid.internal:3128/
    snap-https-proxy: http://squid.internal:3128/

However pulling containers fails until the config on the contarind is also set.

    containerd:
        charm: cs:~containers/containerd
        options:
          http_proxy: http://squid.internal:3128/
          https_proxy: http://squid.internal:3128/

The issue and solution is exactly the same as the original bug description. Is this not released to the charm store?