Docker - nie mogę uruchomić deamona

Odpowiedz Nowy wątek
2018-04-16 09:37
0

Cześć!
Mam ogromny problem z dockerem. Nie mogę uruchomić jego deamona. podczas próby jego uruchomienia dostaję:

dockerd
INFO[2018-04-16T09:35:46.054942906+02:00] libcontainerd: started new docker-containerd process  pid=21656
INFO[0000] starting containerd                           module=containerd revision=773c489c9c1b21a6d78b5c538cd395416ec50f88 version=v1.0.3
INFO[0000] loading plugin "io.containerd.content.v1.content"...  module=containerd type=io.containerd.content.v1
INFO[0000] loading plugin "io.containerd.snapshotter.v1.btrfs"...  module=containerd type=io.containerd.snapshotter.v1
WARN[0000] 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" module=containerd
INFO[0000] loading plugin "io.containerd.snapshotter.v1.overlayfs"...  module=containerd type=io.containerd.snapshotter.v1
INFO[0000] loading plugin "io.containerd.metadata.v1.bolt"...  module=containerd type=io.containerd.metadata.v1
WARN[0000] 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" module="containerd/io.containerd.metadata.v1.bolt"
INFO[0000] loading plugin "io.containerd.differ.v1.walking"...  module=containerd type=io.containerd.differ.v1
INFO[0000] loading plugin "io.containerd.gc.v1.scheduler"...  module=containerd type=io.containerd.gc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.containers"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.content"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.diff"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.events"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.healthcheck"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.images"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.leases"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.namespaces"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.snapshots"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.monitor.v1.cgroups"...  module=containerd type=io.containerd.monitor.v1
INFO[0000] loading plugin "io.containerd.runtime.v1.linux"...  module=containerd type=io.containerd.runtime.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.tasks"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.version"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.introspection"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] serving...                                    address="/var/run/docker/containerd/docker-containerd-debug.sock" module="containerd/debug"
INFO[0000] serving...                                    address="/var/run/docker/containerd/docker-containerd.sock" module="containerd/grpc"
INFO[0000] containerd successfully booted in 0.007348s   module=containerd
ERRO[2018-04-16T09:35:46.318603395+02:00] 'overlay' not found as a supported filesystem on this host. Please ensure kernel is new enough and has overlay support loaded.
ERRO[2018-04-16T09:35:46.321272231+02:00] 'overlay' not found as a supported filesystem on this host. Please ensure kernel is new enough and has overlay support loaded.
INFO[2018-04-16T09:35:46.334031676+02:00] Graph migration to content-addressability took 0.00 seconds
WARN[2018-04-16T09:35:46.337419439+02:00] Your kernel does not support swap memory limit
WARN[2018-04-16T09:35:46.337438494+02:00] Your kernel does not support memory reservation
WARN[2018-04-16T09:35:46.337452567+02:00] Your kernel does not support oom control
WARN[2018-04-16T09:35:46.337465274+02:00] Your kernel does not support memory swappiness
WARN[2018-04-16T09:35:46.337479319+02:00] Your kernel does not support kernel memory limit
WARN[2018-04-16T09:35:46.337488145+02:00] Unable to find cpu cgroup in mounts
WARN[2018-04-16T09:35:46.337501250+02:00] Your kernel does not support cgroup blkio weight
WARN[2018-04-16T09:35:46.337515483+02:00] Your kernel does not support cgroup blkio weight_device
WARN[2018-04-16T09:35:46.337528836+02:00] Your kernel does not support cgroup blkio throttle.read_bps_device
WARN[2018-04-16T09:35:46.337542675+02:00] Your kernel does not support cgroup blkio throttle.write_bps_device
WARN[2018-04-16T09:35:46.337556361+02:00] Your kernel does not support cgroup blkio throttle.read_iops_device
WARN[2018-04-16T09:35:46.337571999+02:00] Your kernel does not support cgroup blkio throttle.write_iops_device
WARN[2018-04-16T09:35:46.337589881+02:00] Unable to find cpuset cgroup in mounts
WARN[2018-04-16T09:35:46.337656042+02:00] mountpoint for pids not found
Error starting daemon: Devices cgroup isn't mounted

Dodanie cgroup przez :

apt-get install cgroupfs-mount

również nie przyniosło rezultatu.
uname -a zwraca:

Linux xxx 3.16.0-042stab127.2 #1 SMP Thu Jan 4 16:41:44 MSK 2018 x86_64 GNU/Linux

Macie jakieś pomysły?

edytowany 1x, ostatnio: NickOver, 2018-04-16 09:37

Pozostało 580 znaków

2018-04-16 10:30
2

Log mówi o

ERRO[2018-04-16T09:35:46.318603395+02:00] 'overlay' not found as a supported filesystem on this host. Please ensure kernel is new enough and has overlay support loaded.

https://wiki.archlinux.org/index.php/Overlay_filesystem mówi, że wsparcie dla overlay jest od kernela 3.18, zaś Twój kernel to 3.16.

Pozostało 580 znaków

2018-04-16 16:50
0

Orientujesz się może czy istnieje docker który nie potrzebuje overlayfs? Niestety nie możemy zrobić upgrade serwera :/

Pozostało 580 znaków

2018-04-17 08:39
0

1) Możesz spróbować skonfigurować jakiś inny storage driver dla dockera: https://docs.docker.com/stora[...]driver/select-storage-driver/
Lokalizacja plików pewnie może się różnić pewnie per dystrybucja Linuksa. To samo dotyczy wersji dockera.

2) Pozostawanie przy 3.16 to tylko kilka problemów ;-) https://www.cvedetails.com/ve[...]inux-Linux-Kernel-3.16.0.html
Może to jakiś argument dla osób decyzyjnych w kwestii "możliwość upgrade", a może dostawca upiera się, że podbicie kernela to utrata gwarancji.

Powodzenia :-)

Pozostało 580 znaków

Odpowiedz
Liczba odpowiedzi na stronę

1 użytkowników online, w tym zalogowanych: 0, gości: 1, botów: 0