Error response from daemon: unknown or invalid runtime name: runsc.

[Frank Micro]

I encountered a Docker runtime error when trying to run with runsc. I wrote it in /etc/docker/daemon.json 
{
    "runtimes": {
    "runsc": {
      "path": "/usr/local/bin/runsc",
      "runtimeArgs": []
    }
  }
}

and then restarted docker several times, but when I looked at the run, there were still only two and no runsc.

Also, when I use docker info --format '{{.SecurityOptions}}'

Command, seccomp is confined to the unconfined space, on which the docker info | grep -i runtimes command is confined, on which an error WARNING is displayed: daemon is not using the default seccomp profile, but I also went to github and downloaded default.json and put it there under /etc/docker

[Kevin Krakauer]

Hi Frank,

- Are you following the quick start?

- What does your /etc/docker/daemon.json look like?

- After you restart Docker via `sudo systemctl restart docker`, what's the output of `docker info | grep Runtimes`?

Kevin

[Frank Micro]

Hi Kevin,

- Yes, I follow the quick Start

- this is my /etc/docker/daemon.json look like

`{

    "runtimes": {
    "runsc": {
      "path": "/usr/local/bin/runsc",
      "runtimeArgs": []
    }
  }

}`
- When I restart docker, output of `docker info | grep Runtimes` is 

`WARNING: daemon is not using the default seccomp profile

 Runtimes: io.containerd.runc.v2 runc`

[Kevin Krakauer]

Well, the runtime is definitely in your daemon.json. Maybe Docker isn't using the default config file? What do you see when running:

ps aux | grep dockerd

Perhaps the --config-file flag is set.

[Frank Micro]

When running:
ps aux | grep dockerd

the output is

root 1525 0.1 0.4 2504528 74752 ? Ssl 08:05 0:00 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock 

frank 4141 0.0 0.0 12308 2816 pts/0 S+ 08:08 0:00 grep --color=auto dockerd

[Kevin Krakauer]

I'm honestly at a bit of a loss here -- I'm not sure why docker wouldn't pick up on the other runtime.

What's the output of `uname -a`?

[Etienne Perot]

I believe this was figured out on GitHub.

--
You received this message because you are subscribed to the Google Groups "gVisor Users [Public]" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gvisor-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gvisor-users/0c7b2261-cce3-48dc-8c0e-63a50ede9cc8n%40googlegroups.com.