-
Notifications
You must be signed in to change notification settings - Fork 489
Description
I have the error failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: unable to setup user: stat /dev/null: no such file or directory: unknown (StartError)
and i identified that should be an architecture issue.
I tried changing the architecture into the provider options, but still the same behaviour.
Seems that that are no option to pull that dockerless image using the desired architecture.
What did you expect to happen instead?
I expect it works normally?
How can we reproduce the bug? (as minimally and precisely as possible)
Install k0s into an ARM64 machine (Oracle Cloud Ampere machines)
Then try to use devpod.
My devcontainer.json:
{
"name": "PlatformIO (Community)",
"build": {
"dockerfile": "Containerfile",
"context": ".",
"args": {
"FEDORA_COMPAT" : "1", // enables fedora compatibility mode (extra dialout group with gid 18)
"VARIANT": "bookworm"
}
},
"customizations": {
"vscode": {
"settings": {
"terminal.integrated.defaultProfile.linux": "zsh"
},
"extensions": [
"ms-vscode.cpptools",
"platformio.platformio-ide"
]
}
},
"forwardPorts": [
8008
],
"mounts": [
"source=/dev/,target=/dev/,type=bind,consistency=consistent"
],
"runArgs": [
"--privileged"
],
"features": {},
"postAttachCommand": "sudo service udev restart"
}
Local Environment:
- DevPod Version: [use
latest] - Operating System: windows
- ARCH of the OS: AMD64
DevPod Provider:
- Kubernetes Provider: k0s on 1.30]
Anything else we need to know?