'bugzilla' failed to build

[ayhoung]

The command [/bin/sh -c yum -y -q install cat /rpm_list && yum clean all] returned a non-zero code: 1

[terabyte]

^^ I am seeing this too. I can pull your most recent image and use it directly, but I cannot build/modify it myself because rpm shits the bed. Looks like the problem might be the centos7 mirrors are F'd, but it is unclear since it is one big giant "rpm install" command.

First step to try to debug might be to separate each package out into its own command and see which (if any) fail. also, maybe, pass -v -v -v -v to yum to have it 'splain what it thinks it is doing.

[terabyte]

(but I am so very very grateful that this thing exists, and thank you very much @dklawren for giving it to us)

[terabyte]

Actually, this is related to this issue I think: https://github.com/docker/docker/issues/6980

This happens during the build when installing "mod_perl". The exact error is:

error: unpacking of archive failed on file /usr/sbin/suexec: cpio: cap_set_file failed - Operation not supported

The main readme already explains the workaround (switch to devicemapper) but implies that it only impacts boot2docker, when in fact it impacts many users of vanilla docker too (i.e. users running centos7 containers from ubuntu 14.04).

[terabyte]

just to update this issue - switching from aufs to vfs lets bugzilla build (but it is sloooow because under vfs each docker command requires a complete copy of the 4GB image).

If you need to build your own image (say, to test bugzilla 5), and you are having this issue (only some OSes have it), add this to /etc/default/docker and restart docker:

DOCKER_OPTS="--storage-driver=vfs"

Note that this will make docker terribly slow. You should flip to this, build the imagine, then do a docker save of the image, flip back, restart docker again, then load the image and you can use it normally.