GitLab

This reverts commit 4371bc4c.

Exposing labels, bin, lib, environment for SCI-F

Spoil the lolcow fun :-( - don't fetch a remote image that user has not requested

Allow empty namespaces for docker:// images

Debian squashfs-tools dependency

Fix to honor user name request for Singularity Hub pull

Fix for NFS+root_squash issue #1068

Packaging: Explicitly include local state directories.

Check if overlay upper/work image directories are symlinks

- Disallow @ in registry (causes ambiguity with @version)
- Disallow @ in tag, so repo:tag@version doesn't parse tag = 'tag@version'
- Allow @ in version, so repo@version@1 will yield version = 'version@1'

This is critial to let namespaces with user privileges
work out of the box.
If the directories are not present, Singularity
will fail, since with user privileges
they can not be created at runtime anymore.
Signed-off-by: Oliver Freyermuth <o.freyermuth@googlemail.com>

Had to bind /var/run/docker.sock inside CentOS container so
it can use the host's docker daemon for testing, see
https://jpetazzo.github.io/2015/09/03/do-not-use-docker-in-docker-for-ci/
for rationale.
Unlike that article, mapping directly to /var/run/docker.sock didn't work
here, cause running CentOS' own /usr/sbin/init mounts another overlayfs
which shadows /var/run/.
Instead, I bound it to /docker.sock, set DOCKER_HOST=unix:///docker.sock
and cleared the path in several places for it to be exported all the way
to the relevant tests.

Now, this would've been a much easier change if the test container started
the build script directly, instead of running /usr/sbin/init, but since
we're trying simulate a full operating system running, doing that would've
reduced the value of the test.

Fix/docker env parsing

always use 'try' for overlayfs functionality.

It's not needed anymore for anything inside the build,
but only to decide whether to test it.
Signed-off-by: Oliver Freyermuth <o.freyermuth@googlemail.com>