containerd can't start with "Argument list too long"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Containerd Subordinate Charm |
New
|
Undecided
|
Unassigned |
Bug Description
While deploying a charmed kubernetes cluster found that containerd units were blocked with message "Container runtime not available"
Checking on the units and containerd was not starting and on journal I could see the error:
/sbin/modprobe: Argument list too long
This was due to juju model-config juju-no-proxy having a too broad subnet resulting in too many IPs printed on containerd.service file:
$ juju model-config juju-no-proxy
localhost,
Updating that modifying /16 subnet with /24 with:
$ juju model-config juju-no-
made containerd starting correctly.
I am not sure how to avoid that but at least charm could potentially identify this issue and be more explicit on the blocked message, to help the operator fixing it.
Thanks for the report. This looks to be a duplicate of https:/ /bugs.launchpad .net/charm- containerd/ +bug/1846551
You can override the no_proxy setting for the containerd charm specifically with something like this:
$ juju config containerd no_proxy= "localhost, 127.0.0. 1,ppa.launchpad .net,launchpad. net,10. 5.0.0/24, 10.245. 164.0/24"