sylabs/singularity: Singularity 3.5.0 Release Candidate 2

This is the second release candidate for the upcoming Singularity v3.5.0, which fixes some regressions found in v3.5.0-rc.1, handling CWD and --nv related paths with symlinks, and custom prompt handling. If you are able to test and give feedback we'd be very grateful as we look toward delivering an awesome and stable 3.5.0 release ahead of the SC19 conference! There are a few new features for 3.5, most notably AMD GPU / ROCm support. We also have a couple of behavior changes noted below. Apart from this many bug fixes and small tweaks have been merged. New features / functionalities New support for AMD GPUs via --rocm option added to bind ROCm devices and libraries into containers. Plugins can now modify Singularity behaviour with two mutators: CLI and Runtime. Introduced the config global command to edit singularity.conf settings from the CLI. Introduced the config fakeroot command to setup subuid and subgid mappings for --fakeroot from the Singularity CLI. Changed defaults / behaviours Go 1.13 adopted. Vendored modules removed from the Git tree, will be included in release tarballs. Singularity will now fail with an error if a requested bind mount cannot be made. This is beneficial to fail fast in workflows where a task may fail a long way downstream if a bind mount is unavailable. Any unavailable bind mount sources must be removed from singularity.conf. Docker/OCI image extraction now faithfully respects layer permissions. This may lead to sandboxes that cannot be removed without modifying permissions. --fix-perms option added to preserve old behaviour when building sandboxes. Discussion issue for this change at: https://github.com/sylabs/singularity/issues/4671 Singularity> prompt is always set when entering shell in a container. The current umask will be honored when building a SIF file. instance exec processes acquire cgroups set on instance start --fakeroot supports uid/subgid ranges >65536 singularity version now reports semver compliant version information. Thanks to our contributors for code, feedback and, testing efforts! As always, please report any bugs to: https://github.com/sylabs/singularity/issues/new If you think that you've discovered a security vulnerability please report it to: security@sylabs.io Have fun