To add more context and an example, this means that deploying on an instance in serverstack (as we do for testing) fails at the microk8s stage. We can workaround for now by running this during this stage:
```
juju config -m admin/controller microk8s containerd_env="\
# This file is managed by Juju. Manual changes may be lost at any time.
# Configure limits for locked memory and maximum number of open files
ulimit -n 65536 || true
ulimit -l 16384 || true
# Uncomment to configure a proxy for containerd
HTTP_PROXY=http://squid.internal:3128
HTTPS_PROXY=http://squid.internal:3128
NO_PROXY=10.0.0.0/8,127.0.0.0/16,192.168.0.0/16
"
```
To add more context and an example, this means that deploying on an instance in serverstack (as we do for testing) fails at the microk8s stage. We can workaround for now by running this during this stage:
``` squid.internal: 3128 squid.internal: 3128 10.0.0. 0/8,127. 0.0.0/16, 192.168. 0.0/16
juju config -m admin/controller microk8s containerd_env="\
# This file is managed by Juju. Manual changes may be lost at any time.
# Configure limits for locked memory and maximum number of open files
ulimit -n 65536 || true
ulimit -l 16384 || true
# Uncomment to configure a proxy for containerd
HTTP_PROXY=http://
HTTPS_PROXY=http://
NO_PROXY=
"
```