Use a workaround from https://github.com/golang/go/issues/15628 for
issues with newer-style vendoring in gcc-go.
Travis's trusty images have gcc-go 4.9, which implements Go 1.2, so it's
missing sync.Pool (introduced in 1.3), so we can't enable the test
there.
Signed-off-by: Nalin Dahyabhai <nalin@redhat.com>
Handle Linux and BSD using different names for the mtime part of a
Stat_t. Add darwin/amd64 to the list of cross-build arches we try
to build during 'make cross'.
Signed-off-by: Nalin Dahyabhai <nalin@redhat.com>
Replace the "autogen" build tag with one named
"containersstorageautogen", to avoid tripping up anyone who vendors the
library but is using that build tag already.
Signed-off-by: Nalin Dahyabhai <nalin@redhat.com>
Add docs and license info for engine-api and uuid, and add net/proxy and
more of vbatts/tar-split. Prune out things which are no longer being
pulled in by our dependencies.
Signed-off-by: Nalin Dahyabhai <nalin@redhat.com>
The coverage bundle really wants the results of integration tests, and
since we don't currently have any, disable it.
Signed-off-by: Nalin Dahyabhai <nalin@redhat.com>
Fixup hack/make/test-unit's ability to figure out which directories
might contain unit tests so that it works outside of a container. Most
of the tests still need root privileges to run, and since they exercise
kernel facilities that require root privileges, that's not likely to
change.
Signed-off-by: Nalin Dahyabhai <nalin@redhat.com>
When cross-compiling, disable device mapper, for which we probably don't
have the libraries that we'd need.
Signed-off-by: Nalin Dahyabhai <nalin@redhat.com>
For now, until we have integration tests, don't try to run them, since
the script that tries to run them fails.
Signed-off-by: Nalin Dahyabhai <nalin@redhat.com>
- Run tests in VMs with sufficiently-new gccgo
- Assume that all binary builds build dynamic binaries
Signed-off-by: Nalin Dahyabhai <nalin@redhat.com>
Rename the library module and CLI wrapper.
Rename daemon/graphdriver to drivers.
Catch up vendoring to match modules we've pruned.
Signed-off-by: Nalin Dahyabhai <nalin@redhat.com>
Rename to cowman (copy-on-write manage, or something), dropping
functions beyond managing raw layers. Since we no longer use the
dockerd layer store, just call them layers.
Signed-off-by: Nalin Dahyabhai <nalin@redhat.com>
Add a simple graph/image/layer store manipulation tool, which can
* create, mount, unmount, and remove read/write layers on the host
* list, load, and save images
* list containers
Signed-off-by: Nalin Dahyabhai <nalin@redhat.com>
The original sed placement was creating packages with an
"unsupported" tag in the package name.
Fixes#24197
Signed-off-by: Christy Perez <christy@linux.vnet.ibm.com>
`make run` allows you to fire up a daemon (in a container) just using
the existing built binaries. This allows for more rapid iteration
instead of dealing with firing up a shell just to start the daemon.
By default the daemon will listen on port 2375 on the default network
interface.
If a port forward is required to access the daemon, the user can set
`make DOCKER_PORT=2375 run` to get a port forward on a random port with
the daemon listening on port 2375, or `make DOCKER_PORT=2375:2375 run`
to get a daemon running with port 2375 forwarded to the daemon running
on 2375.
Note that the daemon is automatically configured to listen on whatever
port is set for the container side of the `DOCKER_PORT` port spec.
When running on docker4mac, the user must do the following:
```
$ make BINDDIR=. DOCKER_PORT=2375 run
```
This makes sure the binaries are loaded in the container and a port is
forwarded, since it is currently impossible to route traffic from the
mac directly to a container IP.
To get a fresh binary:
```
$ make BINDDIR=. DOCKER_PORT=2375 binary run
```
Signed-off-by: Brian Goff <cpuguy83@gmail.com>
This reduces memory usage with a lot of docker proxy processes.
On Docker for Mac we are currently carrying a patch to replace
the binary as we modify it to forward ports to the Mac rather
than the Linux VM, this allows us to simply replace this binary
in our packaging with one that has a compatible interface. This
patch does not provide an easy way to substitute a binary as
the interface is complex and there are few use cases, but where
needed this can be done.
Signed-off-by: Justin Cormack <justin.cormack@docker.com>
error: line 89: Invalid version (epoch must be unsigned integer):
%{epoch}:1.12.0-0.3.rc3.fc24: Requires(pre): docker-engine-selinux >=
%%{epoch}:1.12.0-0.3.rc3.fc24
Signed-off-by: Antonio Murdaca <runcom@redhat.com>
Nalin Dahyabhai