OCI runtime create failed: namespace {"time" ""} does not exist
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3.9k
- Forks
- 230
- Avg merge
- 7h 48m
- Merged PRs (30d)
- 3
Description
After a Linux kernel and docker CE update, container creation fails with error message:
$ docker run --rm --runtime=sysbox-runc hello-world
Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
4f55086f7dd0: Pull complete
d5e71e642bf5: Download complete
Digest: sha256:0e760fdfbc48ba8041e7c6db999bb40bfca508b4be580ac75d32c4e29d202ce1
Status: Downloaded newer image for hello-world:latest
docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: namespace {"time" ""} does not exist
Run 'docker run --help' for more information
Versions:
$ sysbox-runc --version
sysbox-runc
edition: Community Edition (CE)
version: 0.7.0
commit: a4dd414f7b9b7455c0fbf0d5e5db7bcfe30645bc
built at: Tue Mar 3 21:51:47 UTC 2026
built by: Cesar Talledo
oci-specs: 1.1.0+dev
$ docker --version
Docker version 29.5.0, build 98f1464
$ uname -a
Linux aco-tsstage-p 6.8.0-117-generic #117-Ubuntu SMP PREEMPT_DYNAMIC Tue May 5 19:26:24 UTC 2026 x86_64 x86_64 x86_64 GNU/Linux
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=24.04
DISTRIB_CODENAME=noble
DISTRIB_DESCRIPTION="Ubuntu 24.04.4 LTS"
Regressing to sysbox-runc 0.6.7 did not change the situation.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with docker run --rm --runtime=sysbox-runc hello-world on the listed Docker, sysbox-runc, kernel, and Ubuntu versions. Compare the behavior with sysbox-runc 0.6.7 and inspect the runtime creation path implicated by the namespace {"time" ""} does not exist error. Done means container creation succeeds on the reported environment or the incompatibility is precisely identified and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, linux, ubuntu
- Domain
- devops, infrastructure, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100