Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
docker: Error response from daemon: ttrpc: closed: unknown.
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Other Things Gentoo
View previous topic :: View next topic  
Author Message
vootey
n00b
n00b


Joined: 24 Jul 2010
Posts: 42
Location: Austria

PostPosted: Mon Jan 11, 2021 8:15 am    Post subject: docker: Error response from daemon: ttrpc: closed: unknown. Reply with quote

Hi all,

I have a fresh docker installation with
- app-emulation/docker-20.10.2
- app-emulation/docker-cli-20.10.2
- app-emulation/docker-compose-1.28.0_rc2
- app-emulation/containerd-1.4.3-r1

and am struggling with an error thrown at me while testing the hello-world image.
Code:
$ docker run --rm hello-world

returns
Code:
Hello from Docker!
This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:
 1. The Docker client contacted the Docker daemon.
 2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
    (amd64)
 3. The Docker daemon created a new container from that image which runs the
    executable that produces the output you are currently reading.
 4. The Docker daemon streamed that output to the Docker client, which sent it
    to your terminal.

To try something more ambitious, you can run an Ubuntu container with:
 $ docker run -it ubuntu bash

Share images, automate workflows, and more with a free Docker ID:
 https://hub.docker.com/

For more examples and ideas, visit:
 https://docs.docker.com/get-started/

docker: Error response from daemon: ttrpc: closed: unknown.
ERRO[0001] error waiting for container: context canceled


Googling didn't give me much apart from the same error message for a particular version of an arch-linux package which apparently was already fixed quite a while ago, see https://github.com/containerd/containerd/issues/4483.

My docker info:
Code:
$ docker info

Code:
Client:
 Context:    default
 Debug Mode: false

Server:
 Containers: 1
  Running: 0
  Paused: 0
  Stopped: 1
 Images: 7
 Server Version: dev
 Storage Driver: btrfs
  Build Version: Btrfs v5.9
  Library Version: 102
 Logging Driver: journald
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: ea765ab
 runc version: ff819c7e9184c13b7c2607fe6c30ae19403a7aff
 init version: fec3683b971d9c3ef73f284f176672c44b448662 (expected: de40ad007797e0dcd8b7126f27bb87401d224240)
 Security Options:
  seccomp
   Profile: default
  cgroupns
 Kernel Version: 5.4.80-gentoo-r1
 Operating System: Gentoo/Linux
 OSType: linux
 Architecture: x86_64
 CPUs: 8
 Total Memory: 15.59GiB
 Name: [blanked]
 ID: [blanked]
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: No kernel memory TCP limit support
WARNING: No oom kill disable support
WARNING: Support for cgroup v2 is experimental



Any ideas how to fix that problem?
I also tried docker-20.10.1 and also changed to a different (stable) go version and recompiled docker and containerd, but that didn't help.
Back to top
View user's profile Send private message
alamahant
l33t
l33t


Joined: 23 Mar 2019
Posts: 651

PostPosted: Mon Jan 11, 2021 11:52 am    Post subject: Reply with quote

It seems this latest version of containerd is buggy apparently but it is pulled by the unstable version of docker you selected.
Try emerging
Code:

emerge -av =app-emulation/docker-19.03.14

Are iyou running an "unstable" system?
_________________
:)
Back to top
View user's profile Send private message
vootey
n00b
n00b


Joined: 24 Jul 2010
Posts: 42
Location: Austria

PostPosted: Wed Jan 13, 2021 7:13 pm    Post subject: Reply with quote

Yes, I am running a not "stable" system.
Thanks for the hint. Downgrading everything to 19.03.14 helped, the error disappeared.

It's strange though, that I seem to be the only gentoo user with that error.
Back to top
View user's profile Send private message
alamahant
l33t
l33t


Joined: 23 Mar 2019
Posts: 651

PostPosted: Wed Jan 13, 2021 8:23 pm    Post subject: Reply with quote

Indeed
I also installed docker in my unstable system and I didnt get this error with exactly the same versions of docker and caontainerd like you.
Code:

app-emulation/docker-20.10.2
app-emulation/containerd-1.4.3-r1

Strange....
BUT if i run
docker info I get
Code:

Client:
 Context:    default
 Debug Mode: false

Server:
 Containers: 0
  Running: 0
  Paused: 0
  Stopped: 0
 Images: 1
 Server Version: dev
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: ea765ab
 runc version: ff819c7e9184c13b7c2607fe6c30ae19403a7aff
 init version: fec3683b971d9c3ef73f284f176672c44b448662 (expected: de40ad007797e0dcd8b7126f27bb87401d224240)
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 5.10.3
 Operating System: Gentoo/Linux
 OSType: linux
 Architecture: x86_64
 CPUs: 8
 Total Memory: 15.52GiB
 Name: lake.primordial.wisdom
 ID: CLDW:WDKZ:T6E6:HCJ3:KZ5J:PHQO:CUOR:ITKO:MTAN:3ATP:Q32X:2HKN
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: No blkio weight support
WARNING: No blkio weight_device support


I run openrc and you run systemd.
Systemd uses "unified" cgroups config
I use cgroup "legacy" because I need it for lxd.
Maybe that is the issue.
Can you please post the output of
Code:

mount | grep cgroup

?
EDIT Not needed
Quote:

WARNING: Support for cgroup v2 is experimental

Your docker info tells you so.
Maybe you should find a way to enforce cgroup hybrid or legacy mounting by systemd.
i FOUND it.
In
/etc/default/grub
append to the kernel coomand line
Code:
 
systemd.unified_cgroup_hierarchy="false" systemd.legacy_systemd_cgroup_controller="true" ####FOR LEGACY OR
systemd.unified_cgroup_hierarchy="false" systemd.legacy_systemd_cgroup_controller="false" ####FOR HYBRID

and upfate grub and reboot.
Lets see if it fixes the issue.
If not that then it is your btrfs somehow....
_________________
:)
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Other Things Gentoo All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum