Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
runtime: docker build failure with go-1.6.2/musl libc on armhf #16081
Please answer these questions before submitting your issue. Thanks!
Alpine Linux edge.
On wandboard quad with 2G ram and 4G swap.
GOARCH="arm" GOBIN="" GOEXE="" GOHOSTARCH="arm" GOHOSTOS="linux" GOOS="linux" GOPATH="" GORACE="" GOROOT="/usr/lib/go" GOTOOLDIR="/usr/lib/go/pkg/tool/linux_arm" GO15VENDOREXPERIMENT="1" CC="gcc" GOGCCFLAGS="-fPIC -marm -pthread -fmessage-length=0" CXX="g++" CGO_ENABLED="1"
tried to build docker-1.11.2 as:
export AUTO_GOPATH=1 export DOCKER_GITCOMMIT=$_gitcommit export DOCKER_BUILDTAGS=$_buildtags unset CC # prevent possible ccache issues # docker cd "$builddir" ./hack/make.sh dynbinary || return 1
Full build script is found here: http://git.alpinelinux.org/cgit/aports/tree/community/docker/APKBUILD#n62
docker sucessfully built.
What is a bit strange is that it built earlier, with go1.6.1, but after upgrading to go1.6.2 it no longer builds. What is more strange is that i have downgraded various times and now it no longer build with go 1.6.1 either. I get different error messages with different go versions and different docker versions. All seems to be related memory management.
building docker 1.11.1 with go-1.6.2:
buidling docker 1.11.1 with go 1.6.1:
building docker-1.11.2 with go-1.6.2:
Good idea. I asssume you mean with
i did try to backport commit e6ec820 to 1.6 but it did not help. (or my conflict resolving was done bad). I am building
In any case, i will need some kind of workaround since this made it to alpine linux 3.4-stable branch (due to success with
This error means that the runtime set up a bitmap describing all memory in the range
These adjustments could be the result of mmap randomization, which I believe is more aggressive in newer kernels. What are the values of
As was mentioned above, this should be fixed in the upcoming 1.7 release by https://golang.org/cl/20471. But we are not going to backport that to the 1.6 release series.