Please build docker-1.9.0 for arm. about armhf HOT 9 CLOSED

I didn't notice that Dockerfile was modified further. I'll try it again.

I still cannot build it successfully:

Step 26 : RUN set -x    && export GOPATH="$(mktemp -d)"         && git clone https://github.com/docker/notary.git "$GOPATH/src/github.com/docker/notary"   && (cd "$GOPATH/src/github.com/docker/notary" && git checkout -q "$NOTARY_COMMIT")      && GOPATH="$GOPATH/src/github.com/docker/notary/Godeps/_workspace:$GOPATH"                 go build -o /usr/local/bin/notary-server github.com/docker/notary/cmd/notary-server        && rm -rf "$GOPATH"
 ---> Running in e9308c51f18a
+ mktemp -d
+ export GOPATH=/tmp/tmp.sNR3vKhAM1
+ git clone https://github.com/docker/notary.git /tmp/tmp.sNR3vKhAM1/src/github.com/docker/notary
Cloning into '/tmp/tmp.sNR3vKhAM1/src/github.com/docker/notary'...
+ cd /tmp/tmp.sNR3vKhAM1/src/github.com/docker/notary
+ git checkout -q 8e8122eb5528f621afcd4e2854c47302f17392f7
+ GOPATH=/tmp/tmp.sNR3vKhAM1/src/github.com/docker/notary/Godeps/_workspace:/tmp/tmp.sNR3vKhAM1 go build -o /usr/local/bin/notary-server github.com/docker/notary/cmd/notary-server
# github.com/dvsekhvalnov/jose2go/kdf
tmp/tmp.sNR3vKhAM1/src/github.com/docker/notary/Godeps/_workspace/src/github.com/dvsekhvalnov/jose2go/kdf/nist_sp800_56a.go:20: constant 4294967295 overflows int
tmp/tmp.sNR3vKhAM1/src/github.com/docker/notary/Godeps/_workspace/src/github.com/dvsekhvalnov/jose2go/kdf/pbkdf2.go:23: constant 4294967295 overflows int
The command '/bin/sh -c set -x  && export GOPATH="$(mktemp -d)"         && git clone https://github.com/docker/notary.git "$GOPATH/src/github.com/docker/notary"   && (cd "$GOPATH/src/github.com/docker/notary" && git checkout -q "$NOTARY_COMMIT") && GOPATH="$GOPATH/src/github.com/docker/notary/Godeps/_workspace:$GOPATH"              go build -o /usr/local/bin/notary-server github.com/docker/notary/cmd/notary-server        && rm -rf "$GOPATH"' returned a non-zero code: 2
Makefile:75: recipe for target 'build' failed
make: *** [build] Error 1

from armhf.

I'm about to build Docker 1.9.0 for ARMv7, just wait a couple of minutes ...

from armhf.

Thank you very much! 👍

from armhf.

done

from armhf.

😄 I've built docker-1.9.1 successfully on Raspberry Pi 2.

from armhf.

starting with docker version 1.10 docker for arm will be build by the official repository. You can try it with the current development tree.

from armhf.

Uli we built up a 1.9.1 on a bunch of CuBox units and have this consistent devmapper fault that occurs all the time when building images from Dockerfiles. Have you seen that issue? You can succeed in eventually completing images by repeating the docker build until it complete but it is a royal pain.

Not sure which file system would be best for these mx6 arm devices.

Sent from my iPhone

On Jan 16, 2016, at 3:50 AM, Uli Middelberg <[email protected]mailto:[email protected]> wrote:

starting with docker version 1.10 docker for arm will be build by the official repositoryhttps://github.com/docker/docker. You can try it with the current development tree.

Reply to this email directly or view it on GitHubhttps://github.com//issues/13#issuecomment-172194641.

from armhf.

Hi Steve,
hm, this sounds weird. Do you mind opening a new github issue and sharing some information about your environment:

• which device: CuBox (Marvell Armada5XX based) or CuBox-i (Freescale/NXP imx6 based)?
• which kernel (source code repository)?
• the output of check-config.sh

Docker can use several storage backends, the devicemapper is used as a last resort (it's really slow).
I'm using overlayfs on my CuBox-i running a 4.4 vanilla mainline Linux kernel. I haven't used Docker 1.9.1 so far, only 1.9.0 and 1.10.0-dev.

from armhf.

Will do!

Sent from my iPhone

On Jan 17, 2016, at 11:38 AM, Uli Middelberg <[email protected]mailto:[email protected]> wrote:

Hi Steve,
hm, this sounds weird. Do you mind opening a new github issue and sharing some information about your environment:

• which device: CuBox (Marvell Armada5XX based) or CuBox-i (Freescale/NXP imx6 based)?
• which kernel (source code repository)?
• the output of check-config.shhttps://raw.githubusercontent.com/docker/docker/master/contrib/check-config.sh

Docker can use several storage backends, the devicemapper is used as a last resort (it's really slow).
I'm using overlayfs on my CuBox-i running a 4.4 vanilla mainline Linux kernel. I haven't used Docker 1.9.1 so far, only 1.9.0 and 1.10.0-dev.

Reply to this email directly or view it on GitHubhttps://github.com//issues/13#issuecomment-172369906.

from armhf.