-
Notifications
You must be signed in to change notification settings - Fork 582
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
multus daemonset init error: exec: "cp": executable file not found in $PATH: unknown when v4.0.2 #1251
Comments
Thanks for the report... Just a quick note you have a mistmatch with:
and in the init containers
This probably doesn't matter that the cp command isn't in the tagged versions, so, that's worth digging into. Thanks for now the snapshot does address that |
I ran into this same issue before I realized I was using the wrong image. I believe you want to use |
Yeah use this image and update the daemonset to set the command/args correctly on the init container.
|
I ran into this only on arm64 nodes and after some digging, it seems the build pipelines are not working accordingly, resulting in an amd64 image being pulled to arm64 nodes. A manual build image from the latest master works just fine (for ref) The thick images are notably only build for amd64. Is there any historic reason for this? |
What happend:
deploy multus cni(v4.0.2) occur error:
exec: "cp": executable file not found in $PATH: unknown
, but change container image to "multus-cni:snapshot-thick" it working.this multus-cni:v4.0.2 image hash:sha256:ed70b5729dcedf4fcfeefba25cd9d8f43fc7120ac4f768b42ba5de088ad2a509
daemonset config:
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
image path and image ID (from 'docker images') k8snetworkplumbingwg/multus-cni:v4.0.2
kubectl version
): v1.27.10kubectl get net-attach-def -o yaml
)kubectl get pod <podname> -o yaml
)The text was updated successfully, but these errors were encountered: