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
I'm using multus thick and a delegate CNI that needs to request the API: the userspace CNI
I get errors because my delegate CNI searches for the file /var/run/secrets/kubernetes.io/serviceaccount/token but doesn't find it.
I tried to understand what happens exactly, and it seems to me that the issue here is related to the "chroot envrionment" used to run the delegate CNI that can't read the expected files.
I opened a shell in a multus thick daemon, where I can see the expected file, but when I chroot into the /hostroot directory (which is what the daemon does to run the delegate CNI if I'm correct) the files are not visible.
My assumption here is that somehow, the file is not readable from chroot, because it is a symlink or something like that, but don't know chroot very well.
Here you can see in a thick daemon the ls of the files in the container, and in the chroot to see the difference:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
I'm using multus thick and a delegate CNI that needs to request the API: the userspace CNI
I get errors because my delegate CNI searches for the file /var/run/secrets/kubernetes.io/serviceaccount/token but doesn't find it.
I tried to understand what happens exactly, and it seems to me that the issue here is related to the "chroot envrionment" used to run the delegate CNI that can't read the expected files.
I opened a shell in a multus thick daemon, where I can see the expected file, but when I chroot into the /hostroot directory (which is what the daemon does to run the delegate CNI if I'm correct) the files are not visible.
My assumption here is that somehow, the file is not readable from chroot, because it is a symlink or something like that, but don't know chroot very well.
Here you can see in a thick daemon the ls of the files in the container, and in the chroot to see the difference:
In chroot, the files are not visible anymore.
Is this the expected behaviour ?
If yes, how the delegate CNI is supposed to have access to the API to fetch pods for example ?
Beta Was this translation helpful? Give feedback.
All reactions