Docker RPC Error containerd: container did not start be

Discussion about Docker
Locked
User avatar
zpsal
Posts: 5
Joined: 06 Feb 2021, 07:20

Docker RPC Error containerd: container did not start be

Post by zpsal »

Hi,

I've been having trouble connecting to containers initially via TCP but then tried with the docker command (docker exec -ti <ID> sh)

This is the error I'm receiving

[admin@TNAS-015ED4 ~]$ docker exec -ti 40915f75b173 ps
rpc error: code = 2 desc = containerd: container did not start before the specified timeout



[admin@TNAS-015ED4 log]$ tail -500 docker.log
time="2021-02-05T15:16:03.350875529-06:00" level=info msg="libcontainerd: new containerd process, pid: 8658"
time="2021-02-05T15:16:04.737902611-06:00" level=info msg="Graph migration to content-addressability took 0.00 seconds"
time="2021-02-05T15:16:04.738161666-06:00" level=warning msg="Your kernel does not support swap memory limit"
time="2021-02-05T15:16:04.738216667-06:00" level=warning msg="Your kernel does not support cgroup cfs period"
time="2021-02-05T15:16:04.738234236-06:00" level=warning msg="Your kernel does not support cgroup cfs quotas"
time="2021-02-05T15:16:04.738250540-06:00" level=warning msg="Your kernel does not support cgroup rt period"
time="2021-02-05T15:16:04.738266218-06:00" level=warning msg="Your kernel does not support cgroup rt runtime"
time="2021-02-05T15:16:04.738277477-06:00" level=warning msg="Unable to find blkio cgroup in mounts"
time="2021-02-05T15:16:04.738384948-06:00" level=warning msg="mountpoint for pids not found"
time="2021-02-05T15:16:04.738727439-06:00" level=info msg="Loading containers: start."
time="2021-02-05T15:16:05.322539328-06:00" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address"
time="2021-02-05T15:16:05.714791681-06:00" level=info msg="Loading containers: done."
time="2021-02-05T15:16:05.733048278-06:00" level=warning msg="failed to retrieve docker-runc version: unknown output format: runc version commit: 9c2d8d184e5da67c95d601382adf14862e4f2228\nspec: 1.0.0-rc2-dev\n"
time="2021-02-05T15:16:05.733232675-06:00" level=warning msg="failed to retrieve docker-init version: exec: \"docker-init\": executable file not found in $PATH"
time="2021-02-05T15:16:05.733525560-06:00" level=info msg="Daemon has completed initialization"
time="2021-02-05T15:16:05.733567512-06:00" level=info msg="Docker daemon" commit=89658be graphdriver=btrfs version=17.05.0-ce
time="2021-02-05T15:16:05.747051783-06:00" level=info msg="API listen on /var/run/docker.sock"
time="2021-02-05T15:16:33.082765914-06:00" level=warning msg="failed to retrieve docker-runc version: unknown output format: runc version commit: 9c2d8d184e5da67c95d601382adf14862e4f2228\nspec: 1.0.0-rc2-dev\n"
time="2021-02-05T15:16:33.082862341-06:00" level=warning msg="failed to retrieve docker-init version: exec: \"docker-init\": executable file not found in $PATH"
time="2021-02-05T15:16:39.492568801-06:00" level=info msg="Attempting next endpoint for pull after error: error unmarshalling content: invalid character '<' looking for beginning of value"
time="2021-02-05T15:20:06.829481486-06:00" level=error msg="Error running exec in container: rpc error: code = 2 desc = containerd: container did not start before the specified timeout"
time="2021-02-05T15:23:59.389126325-06:00" level=warning msg="failed to retrieve docker-runc version: unknown output format: runc version commit: 9c2d8d184e5da67c95d601382adf14862e4f2228\nspec: 1.0.0-rc2-dev\n"
time="2021-02-05T15:23:59.389227702-06:00" level=warning msg="failed to retrieve docker-init version: exec: \"docker-init\": executable file not found in $PATH"
time="2021-02-05T15:24:06.154997661-06:00" level=info msg="Attempting next endpoint for pull after error: error unmarshalling content: invalid character '<' looking for beginning of value"
time="2021-02-05T16:22:52.196984004-06:00" level=error msg="Error running exec in container: rpc error: code = 2 desc = containerd: container did not start before the specified timeout"
time="2021-02-05T17:04:49.968931327-06:00" level=error msg="Error running exec in container: rpc error: code = 2 desc = containerd: container did not start before the specified timeout"


I've uninstalled and reinstalled docker hoping it would redo everything from fresh, but it doesn't seem to work. I have two TerraMaster devices and this is only on one of them.
User avatar
TMS
TerraMaster Team
Posts: 508
Joined: 20 Oct 2020, 17:06

Re: Docker RPC Error containerd: container did not start be

Post by TMS »

zpsal wrote: 06 Feb 2021, 07:24 [admin@TNAS-015ED4 log]$ tail -500 docker.log
time="2021-02-05T15:16:03.350875529-06:00" level=info msg="libcontainerd: new containerd process, pid: 8658"
time="2021-02-05T15:16:04.737902611-06:00" level=info msg="Graph migration to content-addressability took 0.00 seconds"
time="2021-02-05T15:16:04.738161666-06:00" level=warning msg="Your kernel does not support swap memory limit"
time="2021-02-05T15:16:04.738216667-06:00" level=warning msg="Your kernel does not support cgroup cfs period"
time="2021-02-05T15:16:04.738234236-06:00" level=warning msg="Your kernel does not support cgroup cfs quotas"
time="2021-02-05T15:16:04.738250540-06:00" level=warning msg="Your kernel does not support cgroup rt period"
time="2021-02-05T15:16:04.738266218-06:00" level=warning msg="Your kernel does not support cgroup rt runtime"
Hi,
Show that the kernel does not support, can tell me what TOS system version you are using and the image name.
To contact our tech team, please email to support(at)terra-master.com, remember to replace (at) with @
User avatar
zpsal
Posts: 5
Joined: 06 Feb 2021, 07:20

Re: Docker RPC Error containerd: container did not start be

Post by zpsal »

Hi,
THat machine is a F5-221 using 4.2.08-2101111540.
User avatar
zpsal
Posts: 5
Joined: 06 Feb 2021, 07:20

Re: Docker RPC Error containerd: container did not start be

Post by zpsal »

It seems the container is running- if I build an SSH tunnel to the machine, and proxy my traffic over SOCKS5, I can bring up the Nextcloud session by going to http://172.17.0.1:7670/

But it's slow. Very slow.

It seems it's not forwarding ports and it's not letting me use docker exec to communicate with it.
Locked