You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What would you like to be added:
On some Linux distros (especially ones with read only/immutable file systems) the /run/netns path may not be writable. This is used by the daemonset and causes an error.
This causes an unintuitive error in the daemonset when trying to run a pod
error adding container to network "cbr0": DelegateAdd:
cannot set "" interface name to "eth0": validateIfName: no net namespace /var/run/netns/cni-e05e22ed-dadf-c935-5239-7eb8b4e13169 found: failed to
Statfs "/var/run/netns/cni-e05e22ed-dadf-c935-5239-7eb8b4e13169": no such file or directory
because the daemonset is not able to write to that path.
Why is this needed:
By changing the mount point to /var/run/netns or a similar writable path the daemonset works. Is there a way we could build this logic into the process to verify if it's able to write to that folder and/or mount both paths and verify which path should be written.
I tested this on Talos Linux and changing the mount works.
I'm open to other ideas on how to make this seamless for users.
I don't know for sure but it's possible this also affects Amazon Bottlerocket, Fedora CoreOS, Flatcar Linux, Elemental (Rancher), Kairos. All of them have some form of read only/immutable root file systems.
The text was updated successfully, but these errors were encountered:
What would you like to be added:
On some Linux distros (especially ones with read only/immutable file systems) the
/run/netns
path may not be writable. This is used by the daemonset and causes an error.This causes an unintuitive error in the daemonset when trying to run a pod
because the daemonset is not able to write to that path.
Why is this needed:
By changing the mount point to
/var/run/netns
or a similar writable path the daemonset works. Is there a way we could build this logic into the process to verify if it's able to write to that folder and/or mount both paths and verify which path should be written.I tested this on Talos Linux and changing the mount works.
I'm open to other ideas on how to make this seamless for users.
I don't know for sure but it's possible this also affects Amazon Bottlerocket, Fedora CoreOS, Flatcar Linux, Elemental (Rancher), Kairos. All of them have some form of read only/immutable root file systems.
The text was updated successfully, but these errors were encountered: