Docker Community Forums

Share and learn in the Docker community.

Error when install Docker on Debian 9.4 Stretch

docker

#1

When I use with root permissions: apt-get install docker-ce

I had this error message “Job for containerd.service failed because the control process exited with error code.
See “systemctl status containerd.service” and “journalctl -xe” for details.
containerd.service couldn’t start.”

There are nothing when I use journalctl -xe , just connection informations.

Thank you for your help !


(Martin Terp) #2

Hi :slight_smile:

So the installations goes well?
What if you start “dockerd” manually as root, does it provide any usefull errors?
If not, please paste the output here :slight_smile:


#3

The installations goes well but during it there is error message of last post.

After dockerd :

WARN[2018-12-10T10:39:22.330730622Z] failed to load plugin io.containerd.snapshotter.v1.btrfs error=“path /var/lib/docker/containerd/daemon/io.containerd.snapshotter.v1.btrfs must be a btrfs filesystem to be used with the btrfs snapshotter”
WARN[2018-12-10T10:39:22.331476415Z] failed to load plugin io.containerd.snapshotter.v1.aufs error=“modprobe aufs failed: “modprobe: ERROR: …/libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file ‘/lib/modules/4.9.144-xxxx-std-ipv6-64/modules.dep.bin’\nmodprobe: FATAL: Module aufs not found in directory /lib/modules/4.9.144-xxxx-std-ipv6-64\n”: exit status 1”
WARN[2018-12-10T10:39:22.331847203Z] failed to load plugin io.containerd.snapshotter.v1.zfs error=“path /var/lib/docker/containerd/daemon/io.containerd.snapshotter.v1.zfs must be a zfs filesystem to be used with the zfs snapshotter”

WARN[2018-12-10T10:39:22.331901625Z] could not use snapshotter btrfs in metadata plugin error=“path /var/lib/docker/containerd/daemon/io.containerd.snapshotter.v1.btrfs must be a btrfs filesystem to be used with the btrfs snapshotter”
WARN[2018-12-10T10:39:22.331913700Z] could not use snapshotter aufs in metadata plugin error=“modprobe aufs failed: “modprobe: ERROR: …/libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file ‘/lib/modules/4.9.144-xxxx-std-ipv6-64/modules.dep.bin’\nmodprobe: FATAL: Module aufs not found in directory /lib/modules/4.9.144-xxxx-std-ipv6-64\n”: exit status 1”
WARN[2018-12-10T10:39:22.331925174Z] could not use snapshotter zfs in metadata plugin error=“path /var/lib/docker/containerd/daemon/io.containerd.snapshotter.v1.zfs must be a zfs filesystem to be used with the zfs snapshotter”

WARN[2018-12-10T10:39:22.597138268Z] Your kernel does not support cgroup cfs period
WARN[2018-12-10T10:39:22.597191170Z] Your kernel does not support cgroup cfs quotas
WARN[2018-12-10T10:39:22.597219581Z] Your kernel does not support cgroup rt period
WARN[2018-12-10T10:39:22.597245198Z] Your kernel does not support cgroup rt runtime

WARN[2018-12-10T10:39:22.599277980Z] Running modprobe nf_nat failed with message: modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/4.9.144-xxxx-std-ipv6-64/modules.dep.bin' modprobe: WARNING: Module nf_nat not found in directory /lib/modules/4.9.144-xxxx-std-ipv6-64, error: exit status 1
WARN[2018-12-10T10:39:22.600255892Z] Running modprobe xt_conntrack failed with message: modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/4.9.144-xxxx-std-ipv6-64/modules.dep.bin' modprobe: WARNING: Module xt_conntrack not found in directory /lib/modules/4.9.144-xxxx-std-ipv6-64, error: exit status 1

WARN[2018-12-10T10:39:23.128223925Z] Could not register builder git source: failed to find git binary: exec: “git”: executable file not found in $PATH

I deleted lines of information.


(Martin Terp) #4

What kind of machine are you running this on, and how?

Are you running this on Windows using the subsystems functionality?
Because the WSL is not a full linux kernel, and docker will not run on WSL


#5

I want to install Docker on my dedicated server.

Conf of my server : Debian 9.4 (stretch) x86_64

and i’m connected to it with Putty with ssh access on my Windows 10 PC.


(Martin Terp) #6

Okay, maybe its nothing “important”, there is no ERROR or FATAL in the output? (these are just WARN)