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
Environmental Info:
K3s Version:
k3s version v1.20.2+k3s1 (1d4adb0)
go version go1.15.5
Node(s) CPU architecture, OS, and Version: Linux raspi0 5.4.83-v7l+ #1379 SMP Mon Dec 14 13:11:54 GMT 2020 armv7l GNU/Linux
Cluster Configuration: 1 master, 1 worker
Describe the bug:
When I apply a deployment using a docker container I know to work on this architecture in docker, the container never gets started (persistent crashloopbackoff) and logs the sole error standard_init_linux.go:219: exec user process caused: exec format error
Another deployment running a different container is running fine.
Steps To Reproduce:
Installed K3s: The standard installation script, no flags.
If this is image actually contains arm binaries (although it does not appear to), you need to set the correct architecture when building the image and pushing it to docker hub.
Environmental Info:
K3s Version:
k3s version v1.20.2+k3s1 (1d4adb0)
go version go1.15.5
Node(s) CPU architecture, OS, and Version: Linux raspi0 5.4.83-v7l+ #1379 SMP Mon Dec 14 13:11:54 GMT 2020 armv7l GNU/Linux
Cluster Configuration: 1 master, 1 worker
Describe the bug:
When I apply a deployment using a docker container I know to work on this architecture in docker, the container never gets started (persistent crashloopbackoff) and logs the sole error
standard_init_linux.go:219: exec user process caused: exec format error
Another deployment running a different container is running fine.
Steps To Reproduce:
Expected behavior:
My container starts and runs normally.
Actual behavior:
The container never gets started.
Additional context / logs:
This container runs out of docker fine.
I have ufw installed but have tried disabling it totally and redeploying to no effec.
The text was updated successfully, but these errors were encountered: