Before this patch we would bind mount ${groupDir} as /var/log,
but we wish to put data files in the group dir, so we should move
the logs to a subdirectory.
Signed-off-by: David Scott <dave.scott@docker.com>
Before this patch, docker would only listen on 0.0.0.0:2375 if running
on Hyper-V. This patch makes it listen there on all hypervisors.
In the case of xhyve, it will listen on the host internal vmnet network
or the virtual slirp network. We should aim to replace this with a socket-
based transport instead.
Signed-off-by: David Scott <dave.scott@docker.com>
Before this patch we were using `conn.CloseRead()` and `conn.CloseWrite()`
to flush and signal EOF properly in the proxy, but we forgot to actually
close the file descriptor. As a result we leaked one fd per request,
until the GC came along and closed them for us. This could explain why
the process appeared to block: new connections could not be accepted
because we were out of fds, but once the GC had happened (or we closed
some 9P fds as a result of the client on the host closing its connection)
then the process would unwedge.
This doesn't explain why the 9P filesystem itself would occasionally become
unresponsive in Linux, although apparently still processing requests normally
if you connect to it directly over the host-side socket.
Signed-off-by: David Scott <dave.scott@docker.com>
The busybox adduser and addgroup commands are ignored by docker,
as it avoids symlinks, but they are not compatible so this is
kind of a good idea.
See https://github.com/docker/docker/blob/master/pkg/idtools/usergroupadd_linux.go
However, these do not yet deal with creating mapping ranges in /etc/subuid and
/etc/subgid, so initially we provide a set that match the default docker name
so at least docker daemon --userns-remap=default should work.
Signed-off-by: Justin Cormack <justin.cormack@docker.com>
On Windows, for now we use DOCKER_HOST and access the docker daemon
on Moby via the network.
Signed-off-by: Rolf Neugebauer <rolf.neugebauer@docker.com>
The daemons allow proper shutdown of a VM, heartbeats,
inquiring and setting the network configuratio etc etc.
They are only started with running in a Hyper-V VM
Signed-off-by: Rolf Neugebauer <rolf.neugebauer@docker.com>
