Closed fusion809 closed 7 years ago
Interesting. It appears to be failing inside pacstrap's code, where it tries to set up the build env.
Can you share some more details of your docker environment? Is it possible that your containers aren't being granted mount privileges, or are being otherwise restricted (thinking libseccomp or similar).
I've just confirmed that I'm able to build this still. I'm on docker 1.11 still on that build system, but will test out docker 1.12 tonight.
Will the output of docker version
suffice as a description of my docker environment? If so here it is:
$ docker version
Client:
Version: 1.12.0
API version: 1.24
Go version: go1.6.3
Git commit: 8eab29e
Built: Thu Jul 28 22:11:10 2016
OS/Arch: linux/amd64
as for the mount privileges well how would I test if they aren't? Sorry I'm not an advanced Docker user, I only use Docker occasionally mostly for building Linux packages.
The best bet might be to docker run -ti dock0/arch /bin/bash
and try to use mount or pacstrap yourself, similar to how the makefile is running it. If it fails, that suggests that your configuration is blocking the docker process from mounting filesystems like it needs to
To add to that: the container is being launched by the build process w/ an additional capability:
❯ cat meta/launch
#!/usr/bin/env bash
docker run \
--rm -t -i \
--cap-add=SYS_ADMIN \
-v $SSH_AUTH_SOCK:/auth.sock \
-e SSH_AUTH_SOCK=/auth.sock \
-v $(pwd):/opt/build \
-v ~/.gitconfig:/etc/gitconfig \
arch $1
SYS_ADMIN includes the ability to mount things needed by pacstrap. If that isn't working or has changed in 1.12, that would impact this.
Hi,
I noticed that building
dock0/arch
gave (where$
denotes what I ran and the remaining lines are the corresponding output:Thanks for your time, Brenton