Package Details: docker-git 1:r39078.b5ea9abf25-1

Git Clone URL: (read-only, click to copy)
Package Base: docker-git
Description: Pack, ship and run any application as a lightweight container.
Upstream URL:
Keywords: cgroups containers
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: flaccid
Last Packager: flaccid
Votes: 46
Popularity: 0.000177
First Submitted: 2013-12-05 18:13
Last Updated: 2020-11-08 09:47

Required by (144)

Sources (7)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 ... Next › Last »

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:

They are used with Docker's build system at:

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


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 ( 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.

Anonymous comment 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.

Vi0L0 commented on 2017-01-23 21:34

Built it today for a first time.
After systemctl start docker it wasn't able to start, it was "activating", but never finished, with last line: "containerd: flag provided but not defined: -l"
Using containerd instead of containerd-git would help to start docker but then docker itself doesn't work with error like:
"flag provided but not defined: -console
docker: Error response from daemon: oci runtime error: flag provided but not defined: -console."
Did you guys manage to make it work?

flaccid commented on 2016-11-06 08:59

This package uses master branch which could have bugs anytime and i686 is not supported much anymore upstream.

dluciv commented on 2016-11-06 08:36

Actually, my reason for using this package was not using git snapshot, but just running docker on x86 machine. This package was only one working for me =).

What helped me a lot:

1. I got oficial package from

2. Added i686 to architecture list

3. makepkg && install it

4. Looks working