Package Details: docker-git 1:17.04.0.dev.31005.cf449cf69c-1

Git Clone URL: https://aur.archlinux.org/docker-git.git (read-only)
Package Base: docker-git
Description: Pack, ship and run any application as a lightweight container.
Upstream URL: https://github.com/docker/docker
Keywords: cgroups container lxc
Licenses: Apache License Version 2.0
Conflicts: containerd, containerd-git, docker, runc, runc-git
Provides: docker
Replaces: containerd, containerd-git, docker, runc, runc-git
Submitter: ido
Maintainer: ido (flaccid)
Last Packager: flaccid
Votes: 40
Popularity: 0.496785
First Submitted: 2013-12-05 18:13
Last Updated: 2017-02-18 03:28

Required by (42)

Sources (4)

Latest Comments

joekiller commented on 2017-04-27 21:02

With docker-proxy removed. Inter-container communication is broken via docker-compose is broken. The errors are stuff like:

ERROR: for db Cannot start service db: b'driver failed programming external connectivity on endpoint db_1: exec: "docker-proxy": executable file not found in $PATH'

Per some earlier comments the dynbuild doesn't make the binary but it does appear to be built in the install_binaries script.

Build proxy: https://github.com/moby/moby/blob/50a72c7467ec92cb20b9ec72fd4de2d5e9761347/hack/dockerfile/install-binaries.sh#L41-L47

Commit file: https://github.com/moby/moby/blob/50a72c7467ec92cb20b9ec72fd4de2d5e9761347/hack/dockerfile/binaries-commits#L7

ishitatsuyuki commented on 2017-03-16 03:24

Missing makedepends: linux-headers

In file included from .gopath/src/github.com/docker/docker/daemon/graphdriver/btrfs/btrfs.go:9:0:
/usr/include/btrfs/ctree.h:37:25: fatal error: linux/sizes.h: No such file or directory
#include <linux/sizes.h>
^
compilation terminated.

Installing it doesn't do anything, please check if you're lacking any flags.

flaccid commented on 2017-02-18 03:31

Thanks. I have taken all that into account and now include the specific runc and containerd. Seems to run on my system ok, currently at Docker version 17.04.0-dev, build cf449cf69c!

JP-Ellis commented on 2017-02-10 07:19

@flaccid So looking further into it, I think the issue is with the PKGBUILD and its dependencies. As @cpldave pointed out, docker should be built against specific containerd and runc commits, as specified in:

https://github.com/docker/docker/blob/092cba3/hack/dockerfile/binaries-commits

They are used with Docker's build system at:

https://github.com/docker/docker/blob/092cba3/Dockerfile#L238-L240

Perhaps containerd-git and runc-git could be bundled into the same makepkg as docker-git so that the appropriate commits can be used?

Alternatively, it seems like the preferred way of building Docker is with Docker itself. I'm not sure whether that is possible to do within a PKGBUILD, but could `docker` be a makedepend for `docker-git`?

cpldave commented on 2017-02-09 15:42

@JP-Ellis: I had to hack around with this quite a bit to get it working. I wanted version 1.13.1 of Docker and had to use specific commits from `containerd` and `runc` (as found in https://github.com/docker/docker/blob/092cba3727bb9b4a2f0e922cd6c0f93ea270e363/hack/dockerfile/binaries-commits)

`https://github.com/docker/containerd.git#commit=aa8187dbd3b7ad67d8e5e3a15115d3eef43a7ed1`
`https://github.com/docker/runc.git#commit=9df8b306d01f59d3a8029be411de015b7304dd8f`

For some reason there is a large difference between `docker/*.git` versions of `containerd` and `runc` and the `opencontainers/*.git` versions references in the `containerd-git` and `runc-git` PKGBUILDS. Not sure if they are in sync anymore.

flaccid commented on 2017-02-09 08:20

@JP-Ellis I think take it upstream. The systemd unit is taken from contrib (https://github.com/docker/docker/blob/master/contrib/init/systemd/docker.service) and just calls dockerd.

JP-Ellis commented on 2017-02-08 09:25

Same as @Vi0L0, I seem to be unable to start dockerd (sudo systemctl start docker) as there seems to be some incompatibility with containerd. The error I get is:

```
dockerd[31021]: time="2017-02-08T19:55:42.333312028+11:00" level=info msg="libcontainerd: new containerd process, pid: 31107"
dockerd[31021]: Incorrect Usage. flag provided but not defined: -l
```

and docker just keeps trying to spawn containerd, and containerd keeps exiting. The same happens if I try and launch dockerd manually from the command line.

Do either @flaccid or @ido get this error too? I'll report it upstream if another person has the same issue.

flaccid commented on 2017-01-27 23:50

@ArgylePwnage -git packages use the master branch by default which is 1.14 in dev.

ArgylePwnage commented on 2017-01-27 23:47

Any chance this will get updated to 1.13?

flaccid commented on 2017-01-24 00:11

@Vi0L0 you'd need to take the issue upstream to docker. Unless we have an issue with the packaging here, nothing we can do - master branch is basically dev.

All comments