All workspace builds are getting this:
failed to create shim task: OCI runtime create failed: namespace {"time" ""} does not exist
For example: https://github.com/ddev/coder-ddev/actions/runs/26207226164/job/77109604328#step:7:150
2026-05-21 05:25:25.781Z Error: Unable to start container: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: namespace {"time" ""} does not exist
This is reported and a workaround provided in
There it's reported as sysbox error, @stasadev suggests that it's a new feature in Docker 29.5 that doesn't have sysbox support.
Turning off the time-namespaces feature in /etc/docker/daemon.json fixed this on staging-coder:
{
"data-root": "/data/docker",
"runtimes": {
"sysbox-runc": {
"path": "/usr/bin/sysbox-runc"
}
},
"features": {
"time-namespaces": false
},
"bip": "172.20.0.1/16",
"default-address-pools": [
{
"base": "172.25.0.0/16",
"size": 24
}
]
}
All workspace builds are getting this:
For example: https://github.com/ddev/coder-ddev/actions/runs/26207226164/job/77109604328#step:7:150
This is reported and a workaround provided in
There it's reported as sysbox error, @stasadev suggests that it's a new feature in Docker 29.5 that doesn't have sysbox support.
Turning off the
time-namespacesfeature in /etc/docker/daemon.json fixed this on staging-coder:{ "data-root": "/data/docker", "runtimes": { "sysbox-runc": { "path": "/usr/bin/sysbox-runc" } }, "features": { "time-namespaces": false }, "bip": "172.20.0.1/16", "default-address-pools": [ { "base": "172.25.0.0/16", "size": 24 } ] }