New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docker installation fails E: Can not write log(Is /dev/pts mounted?) #85

Closed
uadev opened this Issue Apr 8, 2016 · 50 comments

Comments

Projects
None yet
@uadev

uadev commented Apr 8, 2016

root@localhost:/mnt/c/apps/cmder# apt-get install docker
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  docker
0 upgraded, 1 newly installed, 0 to remove and 10 not upgraded.
Need to get 0 B/12.2 kB of archives.
After this operation, 65.5 kB of additional disk space will be used.
E: Can not write log (Is /dev/pts mounted?) - openpty (2: No such file or directory)
Selecting previously unselected package docker.
(Reading database ... 24948 files and directories currently installed.)
Preparing to unpack .../docker_1.5-1_amd64.deb ...
Unpacking docker (1.5-1) ...
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Setting up docker (1.5-1) ...
root@localhost:/mnt/c/apps/cmder# docker
The program 'docker' is currently not installed. You can install it by typing:
apt-get install docker
root@localhost:/mnt/c/apps/cmder#
@mphaney

This comment has been minimized.

mphaney commented Apr 8, 2016

Seems to be related to #80. I'm not convinced that the log error is causing docker to fail to install (but what do I know, I'm just some random guy on the Internet), but it nevertheless isn't working, just as you say.

@russalex

This comment has been minimized.

Contributor

russalex commented Apr 9, 2016

The logs error is known and is a red herring, sorry. Docker does not run on WSL at this time. it is something on our radar but not something we want to talk about quite yet. That said, if someone wants to play with Docker here's what they will see:

  1. Docker install instructions are here. Follow the instructions for Trusty 14.04 (LTS)
  2. Starting the Docker service gives the following error (you also see this error on the apt-get install docker-engine when it tries to start the service):

$ sudo service docker start
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: No such fi
le or directory

  • Starting Docker: docker [ OK ]

While it says the Docker service is started, don't be fooled:

$ sudo docker run hello-world
docker: Cannot connect to the Docker daemon. Is the docker daemon running on this host?.
See 'docker run --help'.

@uadev

This comment has been minimized.

uadev commented Apr 9, 2016

@russalex You've managed to run upstart somehow? Is there an instruction for this?

@mjoppich

This comment has been minimized.

mjoppich commented Apr 11, 2016

@russalex it'd be interesting to see how you overcame upstart ...

@russalex

This comment has been minimized.

Contributor

russalex commented Apr 12, 2016

Hate to say it, but I did nothing special for upstart. Before running this test I uninstalled using lxrun /uninstall, then did my usual round of apt-get installs for update, upgrade, build-essential, git and ruby. After that I just followed the instructions on the webpage. What I believe you're seeing is an error that was a result of #143.

Running docker with the apt-get fixes on that thread it looks like:

russ@RUSSALEX-DESK:~$ sudo service docker start
 * Starting Docker: docker                                                         [ OK ]
russ@RUSSALEX-DESK:~$ sudo docker run hello-world
docker: Cannot connect to the Docker daemon. Is the docker daemon running on this host?.
See 'docker run --help'.

@russalex russalex closed this Apr 12, 2016

@russalex russalex reopened this Apr 12, 2016

@mjoppich

This comment has been minimized.

mjoppich commented Apr 13, 2016

Thanks for the heads up.

Even though the service seems to start at my end, something else must be broken, as not even

root@localhost:~# docker -D info ^Croot@localhost:~# docker --help ^Croot@localhost:~#

info or help are displayed. I guess this got to do with docker itself which requires Kernel 3.10+. Is there any chance we get a more recent kernel for WSL?

Coming from computer science, I really think the ability to run docker containers and any other linux tools could really boost bioinformatics, where there are also a lot of non-computer-affine people :)

@tkelman

This comment has been minimized.

tkelman commented Apr 13, 2016

WSL isn't a Linux kernel, it's an emulation layer. Though good question what kernel ABI version is being targeted. Presumably things may need to be updated a bit when the Ubuntu version gets dist-upgraded from 14.04 to 16.04.

@tacnoman

This comment has been minimized.

tacnoman commented Apr 25, 2016

Someone made the Docker work?

@russalex

This comment has been minimized.

Contributor

russalex commented May 16, 2016

The docker engine is not a supported scenario in the short term. I would suggest hitting our User Voice page and upvoting Docker if you're looking to run the docker engine.

The docker client however should be running in build 14342. I have been able to run the docker client and connect to a docker engine running in a VM.

@russalex russalex added the feature label May 16, 2016

@yarmand

This comment has been minimized.

yarmand commented May 29, 2016

To help future work, here is my investigation.
I installed latest docker-engine following instruction at:
https://docs.docker.com/engine/installation/linux/ubuntulinux/

issues:

  • The doc specify a kernel version 3.10 minimum when lxss is 3.0.4+
  • when daemon is starting it fails with error:
FATA[0000] can't create unix socket /var/run/docker.sock: listen unix /var/run/docker.sock: setsockopt: invalid argument

The strace reveal invalid argument on setsockopt:

sudo strace docker daemon
...
setsockopt(4, SOL_SOCKET, SO_BROADCAST, [1], 4) = -1 EINVAL (Invalid argument)
close(4)
...

value 1 as Boolean flag seems fine for SO_BROADCAST when looking at man 7 socket

@davetropeano

This comment has been minimized.

davetropeano commented Jul 21, 2016

@aseering

This comment has been minimized.

Contributor

aseering commented Jul 21, 2016

For what it's worth: A big piece of docker-engine actually lives inside the kernel itself. That's why it keeps requiring newer kernels. (The docker-engine process doesn't actually do a whole lot itself when running a container; its job is to tell the kernel what to do, the kernel does the real work.)

WSL is a clean-room kernel reimplementation. So it can't, for both technical and legal reasons, simply take the kernel components of Docker and "make it work". They would need to reverse-engineer years of ongoing kernel development and reimplement it. (Or take some other nontrivial approach.)

If I were a WSL dev (which I'm not), I would totally enjoy that project. But it would take me a huge amount of time, time that could be spent building many other big features.

@benhillis

This comment has been minimized.

Member

benhillis commented Jul 21, 2016

@aseering Great explanation. Without making any promises I can say that we know docker is an important and powerful too and definitely something we're looking into.

@krisbulman

This comment has been minimized.

krisbulman commented Aug 3, 2016

I can confirm the issue from May posted by @yarmand is still the same as it is today.

$ docker -D info

Cannot connect to the Docker daemon. Is the docker daemon running on this host?
$ sudo docker daemon

can't create unix socket /var/run/docker.sock: listen unix /var/run/docker.sock: setsockopt: invalid argument
$ sudo strace docker daemon

...
setsockopt(4, SOL_SOCKET, SO_BROADCAST, [1], 4) = -1 EINVAL (Invalid argument)
close(4)                                = 0
...
@bbarker

This comment has been minimized.

bbarker commented Aug 11, 2016

It seems like (1) supporting windows server containers in Windows 10 and (2) using Windows Docker from Windows Bash (already working) would be acceptable.

@yarmand

This comment has been minimized.

yarmand commented Aug 11, 2016

@bbarker I do not understand the benefit you are describing. Being able to run docker client inside WSL in order to run a windows app as a container looks a bit overcomplicated to me.
The point we try to make here is being able to run Linux containers without the need of a VM.

It also seems the first error we are blocking on here, is a better support for sockets into WSL, which will be a good thing to have anyway.

@bbarker

This comment has been minimized.

bbarker commented Aug 11, 2016

@yarmand I agree for not needing a VM - this is why I said support windows server containers, which I believe does not require Hyper-V (source). As for being complicated, it really wasn't - I got it up and running in a matter of minutes. Of course, in my case, I was using Hyper-V as I'm on Windows 10.

I'm all for better Linux kernel emulation, just saying this might be an easier route. I'd like to have real containers on Windows 10 instead of using Hyper-V, though I realize that is an "upstream" concern.

Edit: that said, I'm not actually sure, since I haven't tested it, if you can run a Linux container on Windows server containers without hyper-v .... logic suggests no. In which case, full steam ahead on this issue! 👍

Edit 2: Actually, you should be able to run a Windows container with WSL inside windows server containers - over-complicated, yes, I see your point, but it would be better than nothing. Might not be so bad if other distributions were supported in WSL, other than just Ubuntu - but I Haven't looked into this yet.

@fpqc

This comment has been minimized.

fpqc commented Aug 27, 2016

@aseering Does docker use anything in the kernel other than cgroups, namespaces, chroot, and more socket options for AF_Unix? If those are all that are being used, doesn't docker support come practically for free from support for chroot and systemd? I took a look at some of how docker works, and it seems that unlike some of the other container solutions, it doesn't require specific kernel patches.

@aseering

This comment has been minimized.

Contributor

aseering commented Aug 27, 2016

@fpqc -- I don't know the full list offhand, but I know it also does a bunch of stuff with the kernel network layer. It creates virtual network devices (related to tap/tun devices, I think?, which as you've said are very low priority right now). It creates a virtual network bridge (same syscalls as brctl, as far as I know). It uses iptables for routing network traffic between containers.

WSL's socket implementation is in general not robust enough yet. Docker can run over TCP today; but even in that scenario, which is in theory supported, Docker puts a fair bit of stress on the socket, especially when building new containers (it has a client/server model so sends all filesystem data over the network) and there are still bugs/deadlocks in WSL's socket implementation ( #30 #575 ) that cause it to intermittently hang. And, of course, it prefers and defaults to AF_UNIX, which still needs more functionality as you mentioned.

It also does bind-mounts of both directories and files, I believe. Bind-mounts ought to be easy to implement, I think? But I don't think they work yet.

WSL would have to implement the requirements for at least one of the storage backends -- one of AUFS, OverlayFS, BtrFS's snapshotting capabilities, or the whole DeviceMapper subsystem plus loopback devices and mount support for ext4, etc. I think there is a backend that mostly works on just a regular filesystem, but I believe it's firmly labeled as not for production use / mostly just for debugging Docker -- Docker uses copy-on-write semantics extensively; emulating that is expensive and a pain to get right.

Also, there's "supports cgroups and namespaces" and then there's "supports cgroups and namespaces" :-) My understanding, which may be incorrect, is that systemd only really requires pretty basic support for both, at least to get it minimally working. Enumerating the available cgroups, setting some values, etc. Docker uses both cgroups and namespaces extensively; I would be surprised if it worked properly without relatively complete support for the network namespace; I don't know offhand about other namespaces. Docker uses cgroups to impose various restrictions on the processes within a container; I don't have a clear picture in my head of exactly how it uses cgroups, but my guess is that basic containers would mostly work with stubbed-out support there, but they would be somewhat flaky and wouldn't support a bunch of Docker's resource-limiting features without more complete support.

You're right that Docker doesn't require specific kernel patches. For perspective, though: In the US at least, Red Hat Enterprise Linux is the most popular enterprise Linux solution. And RHEL 6 (or its free counterpart CentOS 6) is the most common version in existing deployments. So there's a huge market pressure to support RHEL 6 -- lots of big companies would be willing to pay someone to make it work. Docker never supported RHEL 6.4 or older because its kernel simply lacked necessary functionality. They worked with Red Hat to backport some network-namespace-related stuff from newer kernels into the CentOS 6.5 and 6.6 kernels, but that effort proved to be buggy and insufficient so they have since dropped support for RHEL 6 entirely. (Though Red Hat will happily sell you Docker support and extra features on RHEL 7 :-) ) Docker doesn't require patches because they're working with, and extending, features that are baked into the core kernel. As I recall, networking was an issue at one point, as was capping physical memory (Linux has supported virtual-memory caps for a long time but I believe physical-memory caps are more recent). Other things too, I'm sure. These days, I think it's filesystem stuff; their OverlayFS doc hints a little bit about the kinds of new kernel functionality that they're using. WSL is keeping the Windows kernel team busy, but the Linux kernel team is busy too :-)

@fpqc

This comment has been minimized.

fpqc commented Aug 27, 2016

@aseering I have to admit, I wouldn't be very surprised if MS decides to wait until something like Redstone 3 or Redstone 4, after Server 2016 and Windows containers come out, if only because container-mania, if it continues that long, will make it so MS's customers will demand the ability to run both Windows and Linux workloads on a single kernel without any further virtualization.

The difference between RHEL6/CentOS6 is that Windows Server 2016 will not be just LTS. RHEL6 and CentOS6 are using basically an LTS kernel forked from the mainline kernel all the way back in 2009, with only security updates backported, which means no cgroups whatsoever. That's like asking MS to backport Windows Containers back to Windows Server 2008R2. Docker doesn't support kernels that are older probably than cgroupsv2. If it supported cgroupsv1 (not sure how old Docker is), compatibility was dropped because cgroupsv1 was deemed unstable and was removed from the Kernel.

But yeah, the thing you said about the level of cgroups support necessary for docker, as well as docker taking over Linux's network configuration, means that Docker would be hard to support (based on my reading of its Kernel Option requirements listed on the Gentoo wiki). Thanks for your long and detailed answer though.

@aseering

This comment has been minimized.

Contributor

aseering commented Aug 28, 2016

@fpqc -- yeah, good points; I agree :-) Also, yeah, RHEL 6 is running a really old kernel :-) I guess that speaks to the point I was trying to make: WSL supports a lot of Linux functionality that was commonly used back in 2009. So far, its support for kernel functionality introduced more recently is much more limited. So it's in some ways comparable to RHEL 6's kernel. Not a perfect analogy, certainly. But if it's hard to backport Windows Containers to Windows Server 2008R2, I would expect by analogy that it would be hard to backport Linux Containers to the initial release of WSL.

@fpqc

This comment has been minimized.

fpqc commented Aug 28, 2016

@aseering True, but I suspect that since MS has cgroups-like functionality inside of the NT kernel as part of the Windows containers project, they might be able to write a thin layer to implement cgroups, rather than having to emulate everything.

@farmerbean

This comment has been minimized.

farmerbean commented Feb 7, 2017

I'm running Docker for Windows 1.13.0 and WSL - having installed docker into WSL (and having all the fail-whale drama), I can however, run "docker -H localhost:2375 run hello-world" and send other commands from WSL into windows native. Cool. What would be useful here, would be able to edit the DOCKER_OPTS (https://docs.docker.com/engine/admin/), set the daemon to point to the Windows version and then start-up. Surely not too much to ask!

@aseering

This comment has been minimized.

Contributor

aseering commented Feb 7, 2017

Hi @itopiacloud -- unfortunately, DOCKER_OPTS is not respected by the Docker client. That decision is under the control of the Docker project; you might consider bringing it up on their forums.

What you could do, though, would be something like $ alias docker='docker -H localhost:2375'. That wouldn't help inside shell scripts, but it would help at the command line. Or you could write a wrapper script that does the same thing and add it to the front of $PATH. More work, and it still wouldn't be perfect, but it would work in most cases.

@alexlopes

This comment has been minimized.

alexlopes commented Mar 25, 2017

I found a workaround here but you need docker for windows running

@farmerbean

This comment has been minimized.

farmerbean commented Mar 27, 2017

@alexlopes Hah - I've commented much the same on that thread too..

@bkr32

This comment has been minimized.

bkr32 commented May 24, 2017

i keep running into this issue unknown filesystem type 'cgroup'
when trying to start the docker service, can anyone point out a workaround?

@evertramos

This comment has been minimized.

evertramos commented May 28, 2017

I am getting this error on stating docker:

root@home:/# service docker start
mount: unknown filesystem type 'cgroup'
 * Starting Docker: docker                                                                                    [ OK ]
root@home:/# docker run hello-world
docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.
See 'docker run --help'.
root@home:/#

So, there is some problem with cgroup file system:

mount: unknown filesystem type 'cgroup'
@fpqc

This comment has been minimized.

fpqc commented May 28, 2017

yeah, cgroups aren't implemented to my knowledge.

Also, I don't know if cgroupsv2 has been fully rolled out in the Linux kernel, and cgroupsv1 is basically dead. This video has some details on why, if you don't want to sift through the LKML stuff:

https://www.youtube.com/watch?v=PzpG40WiEfM

Basically, the v1 hierarchies made no sense and lots of the controllers would fight against each other for resources (for example, you could give something a ton of memory priority but no disk i/o and it would break virtual memory, etc, or you could give a large amount of cpu with no memory, or you could give a large amount of disk i/o with low memory and you wouldnt have enough memory for buffers to write to disk efficiently or caching reads for efficinet access to frequently used resources), or sometimes didn't do anything at all. The second version is a complete rethink and reimplementation that gets rid of a lot of the implementation showing through and also simplifies the hierarchies and prevents controllers working against each other.

Since WSL isn't actually meant for in-production servers, the team might be able to use a simplified or stubbed-out version of cgroups, or maybe somehow cgroupsv2 maps well onto the existing NT kernel infrastructure. I guess we'll see!

@benhillis

This comment has been minimized.

Member

benhillis commented Aug 18, 2017

Closing this out because as of Creator's Update, docker installs successfully. There are various other issues tracking docker and docker daemon functionality.

@tnguyen14

This comment has been minimized.

tnguyen14 commented Aug 18, 2017

Is the Creator's Update GA?

@benhillis

This comment has been minimized.

Member

benhillis commented Aug 18, 2017

@itaysk

This comment has been minimized.

itaysk commented Aug 18, 2017

@benhillis wait, so we can run linux docker containers on wsl now?

@benhillis

This comment has been minimized.

Member

benhillis commented Aug 18, 2017

@itaysk - This issue is specifically about docker not installing, which as been fixed. There are other issues tracking various docker pieces not working.

@4mitch

This comment has been minimized.

4mitch commented Aug 27, 2017

It seems now we should trace for following issue #2291

@tangyouwo

This comment has been minimized.

tangyouwo commented Dec 8, 2017

@benhillis now i tried install docker-ce according to the official website documentation。
https://docs.docker.com/engine/installation/linux/docker-ce/ubuntu/#install-from-a-package
but run : docker run hello-world
it still : docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.

@benhillis

This comment has been minimized.

Member

benhillis commented Dec 8, 2017

Can you try manually launching the docker daemon before running this command?

@tangyouwo

This comment has been minimized.

tangyouwo commented Dec 8, 2017

@benhillis yeah
i tried to run service docker start ,
and it output: * Starting Docker: docker [ OK ]
but run ps , no ouput any docker's process

@fruch

This comment has been minimized.

fruch commented Dec 8, 2017

dockerd can run on WSL yes, if you'll try running dockerd you'll see the errors.

there are multiple things missing from the kernel in WSL, cgroups is one of them.

I think it would be a killer feature for WSL. but sound like it conflicts with Microsoft selling windows docker support as part of windows 10 pro.

It's it a bit sad that I need to assume such thing.

Can someone from Microsoft end please say it bit more clearly ? what is the direction here ? lots of threads I've seen here around this specific issue.

And I believe it's more then technical question.

Don't get me wrong, Microsoft are entitled to this money, this task of getting docker to work natively is far from being easy nor cheap.

@fpqc

This comment has been minimized.

fpqc commented Dec 9, 2017

@fruch cgroups are a feature of the memory manager, and in Linux non-server systems, they are almost entirely used by Systemd. By the way, Windows containers are not available in Win10 Pro. Hyper-V containers are, and the reason why they are restricted to Win10Pro is because Hyper-V is only available on Win10 Pro.

@fruch

This comment has been minimized.

fruch commented Dec 9, 2017

@fpqc thanks, I actually meant hyper-v (I don't have much need yet for windows containers), and I don't really care much how it works under the hood (A big fat lie..) as long it's working fast and reliable, and have the same features as docker on linux system. and I want for free... (could be nice if it would be free, but 99$ extra for win10pro sounds reasonable enough for me, as long it's working from WSL)

@Paul-Pushkarov

This comment has been minimized.

Paul-Pushkarov commented Apr 2, 2018

This is what I get trying to start dockerd manually:

:/mnt/c/www$ sudo dockerd
WARN[2018-04-02T14:46:43.056552600-07:00] Could not set daemon root propagation to shared, this is not generally critical but may cause some functionality to not work or fallback to less desirable behavior  dir=/var/lib/docker error="invalid argument"
INFO[2018-04-02T14:46:43.091924600-07:00] libcontainerd: started new docker-containerd process  pid=9993
INFO[0000] starting containerd                           module=containerd revision=cfd04396dc68220d1cecbe686a6cc3aa5ce3667c version=v1.0.2
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.095300s   module=containerd
INFO[2018-04-02T14:46:43.410322300-07:00] Graph migration to content-addressability took 0.00 seconds
WARN[2018-04-02T14:46:43.410986500-07:00] Your kernel does not support cgroup memory limit
WARN[2018-04-02T14:46:43.411430700-07:00] Unable to find cpu cgroup in mounts
WARN[2018-04-02T14:46:43.433371200-07:00] Unable to find blkio cgroup in mounts
WARN[2018-04-02T14:46:43.433807500-07:00] Unable to find cpuset cgroup in mounts
WARN[2018-04-02T14:46:43.435181100-07:00] mountpoint for pids not found
Error starting daemon: Devices cgroup isn't mounted
@fpqc

This comment has been minimized.

fpqc commented Apr 3, 2018

No cgroups support right now. I wonder what would happen if it were for all intents and purposes stubbed out.

@therealkenc

This comment has been minimized.

Collaborator

therealkenc commented Apr 3, 2018

I wonder what would happen if it were for all intents and purposes stubbed out.

I say go full Law of WSL Github and ask for this.

@onomatopellan

This comment has been minimized.

onomatopellan commented Apr 25, 2018

Dunno if it has been stubbed out but in build 17134 this is what a working dockerd inside WSL shows at launch:

~$ sudo cgroupfs-mount
~$ sudo dockerd -D
WARN[2018-04-25T11:11:42.595255800+02:00] Could not set daemon root propagation to shared, this is not generally critical but may cause some functionality to not work or fallback to less desirable behavior  dir=/var/lib/docker error="invalid argument"
DEBU[2018-04-25T11:11:42.601339900+02:00] Listener created for HTTP on unix (/var/run/docker.sock)
INFO[2018-04-25T11:11:42.612917800+02:00] libcontainerd: started new docker-containerd process  pid=24
INFO[0000] starting containerd                           module=containerd revision=cfd04396dc68220d1cecbe686a6cc3aa5ce3667c version=v1.0.2
DEBU[0000] changing OOM score to -500                    module=containerd
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.043014s   module=containerd
DEBU[2018-04-25T11:11:42.699461500+02:00] Golang's threads limit set to 29430
DEBU[2018-04-25T11:11:42.713748900+02:00] processing event stream                       module=libcontainerd namespace=plugins.moby
DEBU[2018-04-25T11:11:42.715237000+02:00] Using default logging driver json-file
DEBU[2018-04-25T11:11:42.718873700+02:00] [graphdriver] priority list: [btrfs zfs overlay2 aufs overlay devicemapper vfs]
DEBU[2018-04-25T11:11:42.732072400+02:00] backingFs=<unknown>,  projectQuotaSupported=false
INFO[2018-04-25T11:11:42.733606500+02:00] [graphdriver] using prior storage driver: overlay2
DEBU[2018-04-25T11:11:42.734551400+02:00] Initialized graph driver overlay2
DEBU[2018-04-25T11:11:42.743458500+02:00] Max Concurrent Downloads: 3
DEBU[2018-04-25T11:11:42.743660100+02:00] Max Concurrent Uploads: 5
DEBU[0000] garbage collected                             d=7.088ms module="containerd/io.containerd.gc.v1.scheduler"
INFO[2018-04-25T11:11:42.767489000+02:00] Graph migration to content-addressability took 0.00 seconds
WARN[2018-04-25T11:11:42.768446500+02:00] Your kernel does not support cgroup memory limit
WARN[2018-04-25T11:11:42.768643400+02:00] Unable to find cpu cgroup in mounts
WARN[2018-04-25T11:11:42.769349000+02:00] Unable to find blkio cgroup in mounts
WARN[2018-04-25T11:11:42.770145000+02:00] Unable to find cpuset cgroup in mounts
WARN[2018-04-25T11:11:42.771064300+02:00] mountpoint for pids not found
INFO[2018-04-25T11:11:42.773181200+02:00] Loading containers: start.
DEBU[2018-04-25T11:11:42.776013100+02:00] processing event stream                       module=libcontainerd namespace=moby
DEBU[2018-04-25T11:11:42.777055800+02:00] Option Experimental: false
DEBU[2018-04-25T11:11:42.778158900+02:00] Option DefaultDriver: bridge
DEBU[2018-04-25T11:11:42.778858100+02:00] Option DefaultNetwork: bridge
DEBU[2018-04-25T11:11:42.779528800+02:00] Network Control Plane MTU: 1500
WARN[2018-04-25T11:11:42.794087500+02:00] Running modprobe nf_nat failed with message: `modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/4.4.0-17134-Microsoft/modules.dep.bin'
modprobe: WARNING: Module nf_nat not found in directory /lib/modules/4.4.0-17134-Microsoft`, error: exit status 1
WARN[2018-04-25T11:11:42.803882700+02:00] Running modprobe xt_conntrack failed with message: `modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/4.4.0-17134-Microsoft/modules.dep.bin'
modprobe: WARNING: Module xt_conntrack not found in directory /lib/modules/4.4.0-17134-Microsoft`, error: exit status 1
DEBU[2018-04-25T11:11:42.809342200+02:00] Fail to initialize firewalld: Failed to connect to D-Bus system bus: dial unix /var/run/dbus/system_bus_socket: connect: no such file or directory, using raw iptables instead
DEBU[2018-04-25T11:11:42.842880300+02:00] /sbin/iptables, [--wait -t filter -C FORWARD -j DOCKER-ISOLATION]
DEBU[2018-04-25T11:11:42.854420500+02:00] /sbin/iptables, [--wait -t nat -D PREROUTING -m addrtype --dst-type LOCAL -j DOCKER]
DEBU[2018-04-25T11:11:42.869991600+02:00] /sbin/iptables, [--wait -t nat -D OUTPUT -m addrtype --dst-type LOCAL ! --dst 127.0.0.0/8 -j DOCKER]
DEBU[2018-04-25T11:11:42.886376500+02:00] /sbin/iptables, [--wait -t nat -D OUTPUT -m addrtype --dst-type LOCAL -j DOCKER]
DEBU[2018-04-25T11:11:42.903265400+02:00] /sbin/iptables, [--wait -t nat -D PREROUTING]
DEBU[2018-04-25T11:11:42.916848500+02:00] /sbin/iptables, [--wait -t nat -D OUTPUT]
DEBU[2018-04-25T11:11:42.930671800+02:00] /sbin/iptables, [--wait -t nat -F DOCKER]
DEBU[2018-04-25T11:11:42.944256000+02:00] /sbin/iptables, [--wait -t nat -X DOCKER]
DEBU[2018-04-25T11:11:42.954744300+02:00] /sbin/iptables, [--wait -t filter -F DOCKER]
DEBU[2018-04-25T11:11:42.969543700+02:00] /sbin/iptables, [--wait -t filter -X DOCKER]
DEBU[2018-04-25T11:11:42.981896600+02:00] /sbin/iptables, [--wait -t filter -F DOCKER-ISOLATION-STAGE-1]
DEBU[2018-04-25T11:11:42.996394400+02:00] /sbin/iptables, [--wait -t filter -X DOCKER-ISOLATION-STAGE-1]
DEBU[2018-04-25T11:11:43.010292800+02:00] /sbin/iptables, [--wait -t filter -F DOCKER-ISOLATION-STAGE-2]
DEBU[2018-04-25T11:11:43.021059400+02:00] /sbin/iptables, [--wait -t filter -X DOCKER-ISOLATION-STAGE-2]
DEBU[2018-04-25T11:11:43.035420800+02:00] /sbin/iptables, [--wait -t filter -F DOCKER-ISOLATION]
DEBU[2018-04-25T11:11:43.048416500+02:00] /sbin/iptables, [--wait -t filter -X DOCKER-ISOLATION]
DEBU[2018-04-25T11:11:43.063324400+02:00] /sbin/iptables, [--wait -t nat -n -L DOCKER]
DEBU[2018-04-25T11:11:43.076938800+02:00] /sbin/iptables, [--wait -t nat -N DOCKER]
DEBU[2018-04-25T11:11:43.088086600+02:00] /sbin/iptables, [--wait -t filter -n -L DOCKER]
DEBU[2018-04-25T11:11:43.101603300+02:00] /sbin/iptables, [--wait -t filter -N DOCKER]
DEBU[2018-04-25T11:11:43.114293300+02:00] /sbin/iptables, [--wait -t filter -n -L DOCKER-ISOLATION-STAGE-1]
DEBU[2018-04-25T11:11:43.128876200+02:00] /sbin/iptables, [--wait -t filter -N DOCKER-ISOLATION-STAGE-1]
DEBU[2018-04-25T11:11:43.142884900+02:00] /sbin/iptables, [--wait -t filter -n -L DOCKER-ISOLATION-STAGE-2]
DEBU[2018-04-25T11:11:43.153590500+02:00] /sbin/iptables, [--wait -t filter -N DOCKER-ISOLATION-STAGE-2]
DEBU[2018-04-25T11:11:43.166785000+02:00] /sbin/iptables, [--wait -t filter -C DOCKER-ISOLATION-STAGE-1 -j RETURN]
DEBU[2018-04-25T11:11:43.180061900+02:00] /sbin/iptables, [--wait -A DOCKER-ISOLATION-STAGE-1 -j RETURN]
DEBU[2018-04-25T11:11:43.194416300+02:00] /sbin/iptables, [--wait -t filter -C DOCKER-ISOLATION-STAGE-2 -j RETURN]
DEBU[2018-04-25T11:11:43.210115500+02:00] /sbin/iptables, [--wait -A DOCKER-ISOLATION-STAGE-2 -j RETURN]
WARN[2018-04-25T11:11:43.233341700+02:00] Could not load necessary modules for IPSEC rules: Running modprobe xfrm_user failed with message: `modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/4.4.0-17134-Microsoft/modules.dep.bin'
modprobe: WARNING: Module xfrm_user not found in directory /lib/modules/4.4.0-17134-Microsoft`, error: exit status 1
WARN[2018-04-25T11:11:43.245351100+02:00] Could not load necessary modules for Conntrack: Running modprobe nf_conntrack failed with message: `modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/4.4.0-17134-Microsoft/modules.dep.bin'
modprobe: WARNING: Module nf_conntrack not found in directory /lib/modules/4.4.0-17134-Microsoft`, error: exit status 1
DEBU[2018-04-25T11:11:43.247256700+02:00] Did not find any interface with name docker0: Link not found
DEBU[2018-04-25T11:11:44.129879300+02:00] Setting bridge mac address to 02:42:b4:57:88:a2
DEBU[2018-04-25T11:11:44.160660400+02:00] Assigning address to bridge interface docker0: 172.17.0.1/16
DEBU[2018-04-25T11:11:47.601489700+02:00] /sbin/iptables, [--wait -t nat -C POSTROUTING -s 172.17.0.0/16 ! -o docker0 -j MASQUERADE]
DEBU[2018-04-25T11:11:47.750246000+02:00] /sbin/iptables, [--wait -t nat -I POSTROUTING -s 172.17.0.0/16 ! -o docker0 -j MASQUERADE]
DEBU[2018-04-25T11:11:47.845845300+02:00] /sbin/iptables, [--wait -t nat -C DOCKER -i docker0 -j RETURN]
DEBU[2018-04-25T11:11:47.865886300+02:00] /sbin/iptables, [--wait -t nat -I DOCKER -i docker0 -j RETURN]
DEBU[2018-04-25T11:11:47.891625100+02:00] /sbin/iptables, [--wait -D FORWARD -i docker0 -o docker0 -j DROP]
DEBU[2018-04-25T11:11:47.909450500+02:00] /sbin/iptables, [--wait -t filter -C FORWARD -i docker0 -o docker0 -j ACCEPT]
DEBU[2018-04-25T11:11:47.932643100+02:00] /sbin/iptables, [--wait -I FORWARD -i docker0 -o docker0 -j ACCEPT]
DEBU[2018-04-25T11:11:47.950639300+02:00] /sbin/iptables, [--wait -t filter -C FORWARD -i docker0 ! -o docker0 -j ACCEPT]
DEBU[2018-04-25T11:11:47.969216500+02:00] /sbin/iptables, [--wait -I FORWARD -i docker0 ! -o docker0 -j ACCEPT]
DEBU[2018-04-25T11:11:47.990205600+02:00] /sbin/iptables, [--wait -t nat -C PREROUTING -m addrtype --dst-type LOCAL -j DOCKER]
DEBU[2018-04-25T11:11:48.013066900+02:00] /sbin/iptables, [--wait -t nat -A PREROUTING -m addrtype --dst-type LOCAL -j DOCKER]
DEBU[2018-04-25T11:11:48.036219600+02:00] /sbin/iptables, [--wait -t nat -C OUTPUT -m addrtype --dst-type LOCAL -j DOCKER ! --dst 127.0.0.0/8]
DEBU[2018-04-25T11:11:48.060583400+02:00] /sbin/iptables, [--wait -t nat -A OUTPUT -m addrtype --dst-type LOCAL -j DOCKER ! --dst 127.0.0.0/8]
DEBU[2018-04-25T11:11:48.086608400+02:00] /sbin/iptables, [--wait -t filter -C FORWARD -o docker0 -j DOCKER]
DEBU[2018-04-25T11:11:48.104493800+02:00] /sbin/iptables, [--wait -I FORWARD -o docker0 -j DOCKER]
DEBU[2018-04-25T11:11:48.127833100+02:00] /sbin/iptables, [--wait -t filter -C FORWARD -o docker0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT]
DEBU[2018-04-25T11:11:48.156426100+02:00] /sbin/iptables, [--wait -I FORWARD -o docker0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT]
DEBU[2018-04-25T11:11:48.178742800+02:00] /sbin/iptables, [--wait -t filter -C FORWARD -j DOCKER-ISOLATION-STAGE-1]
DEBU[2018-04-25T11:11:48.196200900+02:00] /sbin/iptables, [--wait -I FORWARD -j DOCKER-ISOLATION-STAGE-1]
DEBU[2018-04-25T11:11:48.211537500+02:00] /sbin/iptables, [--wait -t filter -C DOCKER-ISOLATION-STAGE-1 -i docker0 ! -o docker0 -j DOCKER-ISOLATION-STAGE-2]
DEBU[2018-04-25T11:11:48.226562200+02:00] /sbin/iptables, [--wait -t filter -I DOCKER-ISOLATION-STAGE-1 -i docker0 ! -o docker0 -j DOCKER-ISOLATION-STAGE-2]
DEBU[2018-04-25T11:11:48.242351200+02:00] /sbin/iptables, [--wait -t filter -C DOCKER-ISOLATION-STAGE-2 -o docker0 -j DROP]
DEBU[2018-04-25T11:11:48.257412200+02:00] /sbin/iptables, [--wait -t filter -I DOCKER-ISOLATION-STAGE-2 -o docker0 -j DROP]
DEBU[2018-04-25T11:11:48.396578900+02:00] Network (df587ea) restored
DEBU[2018-04-25T11:11:48.430939500+02:00] Allocating IPv4 pools for network bridge (df587eaa282466cf1894f3de55b85afb308355c67dae12b7cd604c7310be424e)
DEBU[2018-04-25T11:11:48.432190700+02:00] RequestPool(LocalDefault, 172.17.0.0/16, , map[], false)
DEBU[2018-04-25T11:11:48.434852700+02:00] Received set for ordinal 0, start 0, end 0, any false, release false, serial:false curr:0

DEBU[2018-04-25T11:11:48.436879800+02:00] Received set for ordinal 65535, start 0, end 0, any false, release false, serial:false curr:0

DEBU[2018-04-25T11:11:48.440635600+02:00] RequestAddress(LocalDefault/172.17.0.0/16, 172.17.0.1, map[RequestAddressType:com.docker.network.gateway])
DEBU[2018-04-25T11:11:48.441972900+02:00] Received set for ordinal 1, start 0, end 0, any false, release false, serial:false curr:0

DEBU[2018-04-25T11:11:48.461025200+02:00] /sbin/iptables, [--wait -t nat -C POSTROUTING -s 172.17.0.0/16 ! -o docker0 -j MASQUERADE]
DEBU[2018-04-25T11:11:48.476554500+02:00] /sbin/iptables, [--wait -t nat -D POSTROUTING -s 172.17.0.0/16 ! -o docker0 -j MASQUERADE]
DEBU[2018-04-25T11:11:48.504932900+02:00] /sbin/iptables, [--wait -t nat -C DOCKER -i docker0 -j RETURN]
DEBU[2018-04-25T11:11:48.534057000+02:00] /sbin/iptables, [--wait -t filter -C FORWARD -i docker0 -o docker0 -j ACCEPT]
DEBU[2018-04-25T11:11:48.547568000+02:00] /sbin/iptables, [--wait -t filter -C FORWARD -i docker0 ! -o docker0 -j ACCEPT]
DEBU[2018-04-25T11:11:48.564472800+02:00] /sbin/iptables, [--wait -t filter -C FORWARD -o docker0 -j DOCKER]
DEBU[2018-04-25T11:11:48.578390600+02:00] /sbin/iptables, [--wait -t filter -C FORWARD -o docker0 -j DOCKER]
DEBU[2018-04-25T11:11:48.593798400+02:00] /sbin/iptables, [--wait -t filter -C FORWARD -o docker0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT]
DEBU[2018-04-25T11:11:48.613027600+02:00] /sbin/iptables, [--wait -t filter -C FORWARD -o docker0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT]
DEBU[2018-04-25T11:11:48.633036100+02:00] /sbin/iptables, [--wait -t filter -C DOCKER-ISOLATION-STAGE-1 -i docker0 ! -o docker0 -j DOCKER-ISOLATION-STAGE-2]
DEBU[2018-04-25T11:11:48.667579600+02:00] /sbin/iptables, [--wait -t filter -C DOCKER-ISOLATION-STAGE-2 -o docker0 -j DROP]
DEBU[2018-04-25T11:11:48.708263900+02:00] releasing IPv4 pools from network bridge (df587eaa282466cf1894f3de55b85afb308355c67dae12b7cd604c7310be424e)
DEBU[2018-04-25T11:11:48.710900200+02:00] ReleaseAddress(LocalDefault/172.17.0.0/16, 172.17.0.1)
DEBU[2018-04-25T11:11:48.712373000+02:00] Received set for ordinal 1, start 0, end 0, any false, release true, serial:false curr:0

DEBU[2018-04-25T11:11:48.715285800+02:00] ReleasePool(LocalDefault/172.17.0.0/16)
DEBU[2018-04-25T11:11:48.725641500+02:00] cleanupServiceDiscovery for network:df587eaa282466cf1894f3de55b85afb308355c67dae12b7cd604c7310be424e
DEBU[2018-04-25T11:11:48.727289200+02:00] cleanupServiceBindings for df587eaa282466cf1894f3de55b85afb308355c67dae12b7cd604c7310be424e
INFO[2018-04-25T11:11:48.742892500+02:00] 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
DEBU[2018-04-25T11:11:48.745933400+02:00] Allocating IPv4 pools for network bridge (bb4e8928fc1cd3eff6a7c18351a2df23bd76244f49222de7861a04b5aaafd8be)
DEBU[2018-04-25T11:11:48.748311500+02:00] RequestPool(LocalDefault, 172.17.0.0/16, , map[], false)
DEBU[2018-04-25T11:11:48.748724300+02:00] Received set for ordinal 0, start 0, end 0, any false, release false, serial:false curr:0

DEBU[2018-04-25T11:11:48.750953000+02:00] Received set for ordinal 65535, start 0, end 0, any false, release false, serial:false curr:0

DEBU[2018-04-25T11:11:48.754032900+02:00] RequestAddress(LocalDefault/172.17.0.0/16, 172.17.0.1, map[RequestAddressType:com.docker.network.gateway])
DEBU[2018-04-25T11:11:48.760664500+02:00] Received set for ordinal 1, start 0, end 0, any false, release false, serial:false curr:0

DEBU[2018-04-25T11:11:48.764472400+02:00] /sbin/iptables, [--wait -t nat -C POSTROUTING -s 172.17.0.0/16 ! -o docker0 -j MASQUERADE]
DEBU[2018-04-25T11:11:48.781689900+02:00] /sbin/iptables, [--wait -t nat -I POSTROUTING -s 172.17.0.0/16 ! -o docker0 -j MASQUERADE]
DEBU[2018-04-25T11:11:48.855778700+02:00] /sbin/iptables, [--wait -t nat -C DOCKER -i docker0 -j RETURN]
DEBU[2018-04-25T11:11:48.874875800+02:00] /sbin/iptables, [--wait -t nat -I DOCKER -i docker0 -j RETURN]
DEBU[2018-04-25T11:11:48.901768800+02:00] /sbin/iptables, [--wait -D FORWARD -i docker0 -o docker0 -j DROP]
DEBU[2018-04-25T11:11:48.920164500+02:00] /sbin/iptables, [--wait -t filter -C FORWARD -i docker0 -o docker0 -j ACCEPT]
DEBU[2018-04-25T11:11:48.939980300+02:00] /sbin/iptables, [--wait -I FORWARD -i docker0 -o docker0 -j ACCEPT]
DEBU[2018-04-25T11:11:48.961703800+02:00] /sbin/iptables, [--wait -t filter -C FORWARD -i docker0 ! -o docker0 -j ACCEPT]
DEBU[2018-04-25T11:11:48.979273800+02:00] /sbin/iptables, [--wait -I FORWARD -i docker0 ! -o docker0 -j ACCEPT]
DEBU[2018-04-25T11:11:48.993827900+02:00] /sbin/iptables, [--wait -t nat -C PREROUTING -m addrtype --dst-type LOCAL -j DOCKER]
DEBU[2018-04-25T11:11:49.014531200+02:00] /sbin/iptables, [--wait -t nat -A PREROUTING -m addrtype --dst-type LOCAL -j DOCKER]
DEBU[2018-04-25T11:11:49.076721900+02:00] /sbin/iptables, [--wait -t nat -C OUTPUT -m addrtype --dst-type LOCAL -j DOCKER ! --dst 127.0.0.0/8]
DEBU[2018-04-25T11:11:49.250403800+02:00] /sbin/iptables, [--wait -t nat -A OUTPUT -m addrtype --dst-type LOCAL -j DOCKER ! --dst 127.0.0.0/8]
DEBU[2018-04-25T11:11:49.295777200+02:00] /sbin/iptables, [--wait -t filter -C FORWARD -o docker0 -j DOCKER]
DEBU[2018-04-25T11:11:49.325362100+02:00] /sbin/iptables, [--wait -I FORWARD -o docker0 -j DOCKER]
DEBU[2018-04-25T11:11:49.348706400+02:00] /sbin/iptables, [--wait -t filter -C FORWARD -o docker0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT]
DEBU[2018-04-25T11:11:49.472564100+02:00] /sbin/iptables, [--wait -I FORWARD -o docker0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT]
DEBU[2018-04-25T11:11:49.553136800+02:00] /sbin/iptables, [--wait -t filter -C FORWARD -j DOCKER-ISOLATION-STAGE-1]
DEBU[2018-04-25T11:11:49.605236700+02:00] /sbin/iptables, [--wait -I FORWARD -j DOCKER-ISOLATION-STAGE-1]
DEBU[2018-04-25T11:11:49.652535300+02:00] /sbin/iptables, [--wait -t filter -C DOCKER-ISOLATION-STAGE-1 -i docker0 ! -o docker0 -j DOCKER-ISOLATION-STAGE-2]
DEBU[2018-04-25T11:11:49.676518300+02:00] /sbin/iptables, [--wait -t filter -I DOCKER-ISOLATION-STAGE-1 -i docker0 ! -o docker0 -j DOCKER-ISOLATION-STAGE-2]
DEBU[2018-04-25T11:11:49.693239600+02:00] /sbin/iptables, [--wait -t filter -C DOCKER-ISOLATION-STAGE-2 -o docker0 -j DROP]
DEBU[2018-04-25T11:11:49.709315800+02:00] /sbin/iptables, [--wait -t filter -I DOCKER-ISOLATION-STAGE-2 -o docker0 -j DROP]
DEBU[2018-04-25T11:11:49.742059400+02:00] /sbin/iptables, [--wait -t filter -n -L DOCKER-USER]
DEBU[2018-04-25T11:11:49.755250100+02:00] /sbin/iptables, [--wait -t filter -N DOCKER-USER]
DEBU[2018-04-25T11:11:49.769520400+02:00] /sbin/iptables, [--wait -t filter -C DOCKER-USER -j RETURN]
DEBU[2018-04-25T11:11:49.785076100+02:00] /sbin/iptables, [--wait -A DOCKER-USER -j RETURN]
DEBU[2018-04-25T11:11:49.802096700+02:00] /sbin/iptables, [--wait -t filter -C FORWARD -j DOCKER-USER]
DEBU[2018-04-25T11:11:49.844280400+02:00] /sbin/iptables, [--wait -I FORWARD -j DOCKER-USER]
INFO[2018-04-25T11:11:49.965786500+02:00] Loading containers: done.
INFO[2018-04-25T11:11:50.115591400+02:00] Docker daemon                                 commit=fcdc984cfd graphdriver(s)=overlay2 version=dev
INFO[2018-04-25T11:11:50.123806800+02:00] Daemon has completed initialization
DEBU[2018-04-25T11:11:50.130474600+02:00] Registering routers
DEBU[2018-04-25T11:11:50.130769200+02:00] Registering GET, /containers/{name:.*}/checkpoints
DEBU[2018-04-25T11:11:50.132628800+02:00] Registering POST, /containers/{name:.*}/checkpoints
DEBU[2018-04-25T11:11:50.134059600+02:00] Registering DELETE, /containers/{name}/checkpoints/{checkpoint}
DEBU[2018-04-25T11:11:50.135202300+02:00] Registering HEAD, /containers/{name:.*}/archive
DEBU[2018-04-25T11:11:50.137049300+02:00] Registering GET, /containers/json
DEBU[2018-04-25T11:11:50.148288400+02:00] Registering GET, /containers/{name:.*}/export
DEBU[2018-04-25T11:11:50.149952900+02:00] Registering GET, /containers/{name:.*}/changes
DEBU[2018-04-25T11:11:50.156442800+02:00] Registering GET, /containers/{name:.*}/json
DEBU[2018-04-25T11:11:50.165437000+02:00] Registering GET, /containers/{name:.*}/top
DEBU[2018-04-25T11:11:50.166947500+02:00] Registering GET, /containers/{name:.*}/logs
DEBU[2018-04-25T11:11:50.169362800+02:00] Registering GET, /containers/{name:.*}/stats
DEBU[2018-04-25T11:11:50.170522200+02:00] Registering GET, /containers/{name:.*}/attach/ws
DEBU[2018-04-25T11:11:50.174411600+02:00] Registering GET, /exec/{id:.*}/json
DEBU[2018-04-25T11:11:50.178691500+02:00] Registering GET, /containers/{name:.*}/archive
DEBU[2018-04-25T11:11:50.180379300+02:00] Registering POST, /containers/create
DEBU[2018-04-25T11:11:50.182560900+02:00] Registering POST, /containers/{name:.*}/kill
DEBU[2018-04-25T11:11:50.183837800+02:00] Registering POST, /containers/{name:.*}/pause
DEBU[2018-04-25T11:11:50.188405300+02:00] Registering POST, /containers/{name:.*}/unpause
DEBU[2018-04-25T11:11:50.192394400+02:00] Registering POST, /containers/{name:.*}/restart
DEBU[2018-04-25T11:11:50.201153000+02:00] Registering POST, /containers/{name:.*}/start
DEBU[2018-04-25T11:11:50.219840000+02:00] Registering POST, /containers/{name:.*}/stop
DEBU[2018-04-25T11:11:50.226022800+02:00] Registering POST, /containers/{name:.*}/wait
DEBU[2018-04-25T11:11:50.233791300+02:00] Registering POST, /containers/{name:.*}/resize
DEBU[2018-04-25T11:11:50.236957900+02:00] Registering POST, /containers/{name:.*}/attach
DEBU[2018-04-25T11:11:50.241115900+02:00] Registering POST, /containers/{name:.*}/copy
DEBU[2018-04-25T11:11:50.242985200+02:00] Registering POST, /containers/{name:.*}/exec
DEBU[2018-04-25T11:11:50.246301200+02:00] Registering POST, /exec/{name:.*}/start
DEBU[2018-04-25T11:11:50.248707200+02:00] Registering POST, /exec/{name:.*}/resize
DEBU[2018-04-25T11:11:50.250639700+02:00] Registering POST, /containers/{name:.*}/rename
DEBU[2018-04-25T11:11:50.252175300+02:00] Registering POST, /containers/{name:.*}/update
DEBU[2018-04-25T11:11:50.260584800+02:00] Registering POST, /containers/prune
DEBU[2018-04-25T11:11:50.264002700+02:00] Registering POST, /commit
DEBU[2018-04-25T11:11:50.264788900+02:00] Registering PUT, /containers/{name:.*}/archive
DEBU[2018-04-25T11:11:50.265711500+02:00] Registering DELETE, /containers/{name:.*}
DEBU[2018-04-25T11:11:50.266912400+02:00] Registering GET, /images/json
DEBU[2018-04-25T11:11:50.268827700+02:00] Registering GET, /images/search
DEBU[2018-04-25T11:11:50.274352300+02:00] Registering GET, /images/get
DEBU[2018-04-25T11:11:50.275205000+02:00] Registering GET, /images/{name:.*}/get
DEBU[2018-04-25T11:11:50.275983800+02:00] Registering GET, /images/{name:.*}/history
DEBU[2018-04-25T11:11:50.277782400+02:00] Registering GET, /images/{name:.*}/json
DEBU[2018-04-25T11:11:50.278515900+02:00] Registering POST, /images/load
DEBU[2018-04-25T11:11:50.279357900+02:00] Registering POST, /images/create
DEBU[2018-04-25T11:11:50.280105500+02:00] Registering POST, /images/{name:.*}/push
DEBU[2018-04-25T11:11:50.280993100+02:00] Registering POST, /images/{name:.*}/tag
DEBU[2018-04-25T11:11:50.281845400+02:00] Registering POST, /images/prune
DEBU[2018-04-25T11:11:50.287109800+02:00] Registering DELETE, /images/{name:.*}
DEBU[2018-04-25T11:11:50.290302800+02:00] Registering OPTIONS, /{anyroute:.*}
DEBU[2018-04-25T11:11:50.290965200+02:00] Registering GET, /_ping
DEBU[2018-04-25T11:11:50.292007300+02:00] Registering GET, /events
DEBU[2018-04-25T11:11:50.293021600+02:00] Registering GET, /info
DEBU[2018-04-25T11:11:50.293900900+02:00] Registering GET, /version
DEBU[2018-04-25T11:11:50.294772300+02:00] Registering GET, /system/df
DEBU[2018-04-25T11:11:50.299375700+02:00] Registering POST, /auth
DEBU[2018-04-25T11:11:50.300172100+02:00] Registering GET, /volumes
DEBU[2018-04-25T11:11:50.301558300+02:00] Registering GET, /volumes/{name:.*}
DEBU[2018-04-25T11:11:50.302953200+02:00] Registering POST, /volumes/create
DEBU[2018-04-25T11:11:50.303745400+02:00] Registering POST, /volumes/prune
DEBU[2018-04-25T11:11:50.306282200+02:00] Registering DELETE, /volumes/{name:.*}
DEBU[2018-04-25T11:11:50.307136400+02:00] Registering POST, /build
DEBU[2018-04-25T11:11:50.312005100+02:00] Registering POST, /build/prune
DEBU[2018-04-25T11:11:50.313427600+02:00] Registering POST, /session
DEBU[2018-04-25T11:11:50.314669400+02:00] Registering POST, /swarm/init
DEBU[2018-04-25T11:11:50.316103500+02:00] Registering POST, /swarm/join
DEBU[2018-04-25T11:11:50.317364000+02:00] Registering POST, /swarm/leave
DEBU[2018-04-25T11:11:50.318919600+02:00] Registering GET, /swarm
DEBU[2018-04-25T11:11:50.319790900+02:00] Registering GET, /swarm/unlockkey
DEBU[2018-04-25T11:11:50.320402600+02:00] Registering POST, /swarm/update
DEBU[2018-04-25T11:11:50.323087300+02:00] Registering POST, /swarm/unlock
DEBU[2018-04-25T11:11:50.323987600+02:00] Registering GET, /services
DEBU[2018-04-25T11:11:50.324864500+02:00] Registering GET, /services/{id}
DEBU[2018-04-25T11:11:50.325918800+02:00] Registering POST, /services/create
DEBU[2018-04-25T11:11:50.326764500+02:00] Registering POST, /services/{id}/update
DEBU[2018-04-25T11:11:50.327862600+02:00] Registering DELETE, /services/{id}
DEBU[2018-04-25T11:11:50.329260300+02:00] Registering GET, /services/{id}/logs
DEBU[2018-04-25T11:11:50.330595700+02:00] Registering GET, /nodes
DEBU[2018-04-25T11:11:50.331407100+02:00] Registering GET, /nodes/{id}
DEBU[2018-04-25T11:11:50.332095900+02:00] Registering DELETE, /nodes/{id}
DEBU[2018-04-25T11:11:50.332916100+02:00] Registering POST, /nodes/{id}/update
DEBU[2018-04-25T11:11:50.333706900+02:00] Registering GET, /tasks
DEBU[2018-04-25T11:11:50.334583800+02:00] Registering GET, /tasks/{id}
DEBU[2018-04-25T11:11:50.335529700+02:00] Registering GET, /tasks/{id}/logs
DEBU[2018-04-25T11:11:50.337028900+02:00] Registering GET, /secrets
DEBU[2018-04-25T11:11:50.340784300+02:00] Registering POST, /secrets/create
DEBU[2018-04-25T11:11:50.348550100+02:00] Registering DELETE, /secrets/{id}
DEBU[2018-04-25T11:11:50.350191300+02:00] Registering GET, /secrets/{id}
DEBU[2018-04-25T11:11:50.351897700+02:00] Registering POST, /secrets/{id}/update
DEBU[2018-04-25T11:11:50.353303400+02:00] Registering GET, /configs
DEBU[2018-04-25T11:11:50.356773400+02:00] Registering POST, /configs/create
DEBU[2018-04-25T11:11:50.357988700+02:00] Registering DELETE, /configs/{id}
DEBU[2018-04-25T11:11:50.359102100+02:00] Registering GET, /configs/{id}
DEBU[2018-04-25T11:11:50.360239200+02:00] Registering POST, /configs/{id}/update
DEBU[2018-04-25T11:11:50.361722200+02:00] Registering GET, /plugins
DEBU[2018-04-25T11:11:50.362990100+02:00] Registering GET, /plugins/{name:.*}/json
DEBU[2018-04-25T11:11:50.364144900+02:00] Registering GET, /plugins/privileges
DEBU[2018-04-25T11:11:50.365318400+02:00] Registering DELETE, /plugins/{name:.*}
DEBU[2018-04-25T11:11:50.366086900+02:00] Registering POST, /plugins/{name:.*}/enable
DEBU[2018-04-25T11:11:50.367361800+02:00] Registering POST, /plugins/{name:.*}/disable
DEBU[2018-04-25T11:11:50.368671200+02:00] Registering POST, /plugins/pull
DEBU[2018-04-25T11:11:50.369799000+02:00] Registering POST, /plugins/{name:.*}/push
DEBU[2018-04-25T11:11:50.372881800+02:00] Registering POST, /plugins/{name:.*}/upgrade
DEBU[2018-04-25T11:11:50.374121800+02:00] Registering POST, /plugins/{name:.*}/set
DEBU[2018-04-25T11:11:50.375665700+02:00] Registering POST, /plugins/create
DEBU[2018-04-25T11:11:50.376854000+02:00] Registering GET, /distribution/{name:.*}/json
DEBU[2018-04-25T11:11:50.378179700+02:00] Registering GET, /networks
DEBU[2018-04-25T11:11:50.385070400+02:00] Registering GET, /networks/
DEBU[2018-04-25T11:11:50.386194500+02:00] Registering GET, /networks/{id:.+}
DEBU[2018-04-25T11:11:50.390269200+02:00] Registering POST, /networks/create
DEBU[2018-04-25T11:11:50.391452400+02:00] Registering POST, /networks/{id:.*}/connect
DEBU[2018-04-25T11:11:50.393378000+02:00] Registering POST, /networks/{id:.*}/disconnect
DEBU[2018-04-25T11:11:50.397596000+02:00] Registering POST, /networks/prune
DEBU[2018-04-25T11:11:50.398934700+02:00] Registering DELETE, /networks/{id:.*}
INFO[2018-04-25T11:11:50.402572300+02:00] API listen on /var/run/docker.sock
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment