I've encountered this in a test environment where the containerd charm is a dependency. The test environment subnet is a /16 network, and the charm ends up generating a 799501 byte /etc/systemd/system/containerd.service.d/proxy.conf file. This results in "Argument list too long" errors on the containerd systemd service.
I've encountered this in a test environment where the containerd charm is a dependency. The test environment subnet is a /16 network, and the charm ends up generating a 799501 byte /etc/systemd/ system/ containerd. service. d/proxy. conf file. This results in "Argument list too long" errors on the containerd systemd service.