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
1.) Found that the csi containers from quay are not multi-arch, building my own so not a big deal at the moment.
2.) The jparklab/synology-csi:v1.0.0-kubernetes-1.18.0 from the k8s v1.18 deployment (node.yml) is only an amd64 build. You also have a jparklab/synology-csi:v1.18.0 tag that seems to have the multi-arch builds. I edited the daemonset to use the 1.18.0 tag, but also getting a standard_init_linux.go:211: exec user process caused "exec format error" on that image. It seems like something not quite right on the build in addition to the deployment having the incorrect tag for multi-arch use.
Let me know if I can help out in anyway on this, happy to assist with debugging/rebuilding etc.
The text was updated successfully, but these errors were encountered:
I think the problem was that it wasn't compiling across all architectures when those were set. While each of those platforms were being pushed, they were incorrect.
1.) Found that the csi containers from quay are not multi-arch, building my own so not a big deal at the moment.
2.) The jparklab/synology-csi:v1.0.0-kubernetes-1.18.0 from the k8s v1.18 deployment (node.yml) is only an amd64 build. You also have a jparklab/synology-csi:v1.18.0 tag that seems to have the multi-arch builds. I edited the daemonset to use the 1.18.0 tag, but also getting a
standard_init_linux.go:211: exec user process caused "exec format error"
on that image. It seems like something not quite right on the build in addition to the deployment having the incorrect tag for multi-arch use.Let me know if I can help out in anyway on this, happy to assist with debugging/rebuilding etc.
The text was updated successfully, but these errors were encountered: