nestybox / nestybox/sysbox

docker: Error response from daemon: unknown or invalid runtime name: sysbox-runc.

Open
#772 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
3.9k
Forks
230
Avg merge
7h 48m
Merged PRs (30d)
3

Description

➜ sudo systemctl status sysbox -n20
[sudo] password for bitnom:
● sysbox.service - Sysbox container runtime
     Loaded: loaded (/lib/systemd/system/sysbox.service; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2024-01-29 00:24:22 EST; 16h ago
       Docs: https://github.com/nestybox/sysbox
   Main PID: 12047 (sh)
      Tasks: 2 (limit: 13886)
     Memory: 384.0K
     CGroup: /system.slice/sysbox.service
             ├─12047 /bin/sh -c "/usr/bin/sysbox-runc --version && /usr/bin/sysbox-mgr --disable-shiftfs --version && /usr/bin/sysb>
             └─12154 /bin/sleep infinity

Jan 29 00:24:22 DESKTOP-J6N1M4N systemd[1]: Started Sysbox container runtime.
Jan 29 00:24:22 DESKTOP-J6N1M4N sh[12048]: sysbox-runc
Jan 29 00:24:22 DESKTOP-J6N1M4N sh[12048]:         edition:         Community Edition (CE)
Jan 29 00:24:22 DESKTOP-J6N1M4N sh[12048]:         version:         0.6.3
Jan 29 00:24:22 DESKTOP-J6N1M4N sh[12048]:         commit:         e6ca9b930c43c0f20bb93ef3ef6af5bd49fd88ce
Jan 29 00:24:22 DESKTOP-J6N1M4N sh[12048]:         built at:         Mon Jan 29 00:07:49 UTC 2024
Jan 29 00:24:22 DESKTOP-J6N1M4N sh[12048]:         built by:
Jan 29 00:24:22 DESKTOP-J6N1M4N sh[12048]:         oci-specs:         1.1.0+dev
Jan 29 00:24:22 DESKTOP-J6N1M4N sh[12064]: sysbox-mgr
Jan 29 00:24:22 DESKTOP-J6N1M4N sh[12064]:         edition:         Community Edition (CE)
Jan 29 00:24:22 DESKTOP-J6N1M4N sh[12064]:         version:         0.6.3
Jan 29 00:24:22 DESKTOP-J6N1M4N sh[12064]:         commit:         03f5d7bc584fdcb2319b2c1831bd58581185fc1c
Jan 29 00:24:22 DESKTOP-J6N1M4N sh[12064]:         built at:         Mon Jan 29 00:08:12 UTC 2024
Jan 29 00:24:22 DESKTOP-J6N1M4N sh[12064]:         built by:
Jan 29 00:24:22 DESKTOP-J6N1M4N sh[12084]: sysbox-fs
Jan 29 00:24:22 DESKTOP-J6N1M4N sh[12084]:         edition:         Community Edition (CE)
Jan 29 00:24:22 DESKTOP-J6N1M4N sh[12084]:         version:         0.6.3
Jan 29 00:24:22 DESKTOP-J6N1M4N sh[12084]:         commit:         ff6e109d64856db9b4bce8d10226371d7797ba96
Jan 29 00:24:22 DESKTOP-J6N1M4N sh[12084]:         built at:         Mon Jan 29 00:08:07 UTC 2024
Jan 29 00:24:22 DESKTOP-J6N1M4N sh[12084]:         built by:

16:57:12 with bitnom in ~ took 10.8s …
➜ uname -r
5.15.133.1-microsoft-standard-WSL2

17:01:55 with bitnom in ~ …
➜ docker run --runtime=sysbox-runc hello-world
docker: Error response from daemon: unknown or invalid runtime name: sysbox-runc.
See 'docker run --help'.

I compiled the project from git master, and built and installed the .deb file. As you can see I used --disable-shiftfs in an attempt to overcome this issue.

Things I read:
https://github.com/nestybox/sysbox/issues/596#issuecomment-1291235140
https://github.com/nestybox/sysbox/issues/162
https://forums.docker.com/t/sysbox-runc-is-not-working-as-runtime-for-docker-in-ubuntu/134429
https://stackoverflow.com/questions/75343570/sysbox-runc-is-not-working-as-runtime-for-docker-in-ubuntu
https://github.com/nestybox/sysbox/issues/32
https://github.com/nestybox/sysbox-pkgr/pull/121

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reported docker run --runtime=sysbox-runc hello-world failure and reviewing the sysbox.service status and installation details shown in the issue. Check how the installed package registers the runtime with Docker and compare that with the referenced Sysbox discussions. Done means identifying a supported configuration or a reproducible product defect with an appropriate fix or documented resolution.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, shell
Domain
devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.