@bauerm97 bauerm97 released this Sep 20, 2018 · 244 commits to master since this release

Assets 2

Greetings Singularity Folks!

We are pleased to announce the second alpha version of Singularity 3.0. This release is a large improvement over 3.0.0-alpha.1, with major fixes to bugs and feature parity issues. We've also just moved the repository from singularityware/singularity to sylabs/singularity. Nothing should change with this update, but if any complications arise as a result of the move please reach out to us on our slack channel.

It is our intention to quickly iterate, with further alpha and beta releases over the coming weeks. Stay tuned, and as always, we welcome your feedback and contributions!

@tri-adam tri-adam released this Aug 20, 2018 · 844 commits to master since this release

Assets 2

Greetings Singularity Folks!

We are pleased to announce the first alpha version of Singularity 3.0. This release is not for the faint of heart, with bugs must be squashed, features that are not yet complete, and new development environment requirements. On that last point, be sure to check out the installation instructions.

It is our intention to quickly iterate, with further alpha (and eventually beta) releases over the coming weeks. Stay tuned, and as always, we welcome your feedback and contributions!

@GodloveD GodloveD released this Aug 4, 2018 · 2563 commits to master since this release

Assets 3

Greetings Singularity-ers!

It is my great pleasure to announce the release of version 2.6.0! This release has a few bug fixes and lot of cool new features that are detailed below.

Please note that 2.6.0 is expected to be the final feature release in the 2.x series. While bug fixes may be added via point releases (for example 2.6.1) no new features releases (for example 2.7.0) are planned.

Pull requests adding features to the 2.x series will no longer be reviewed. Any new features should be targeted to the master branch (which used to be called development-3.0).

For more information about the reorganization of Singularity branches in the GitHub repo, please see this Sylabs lab notes.

Thanks and have fun!

Implemented enhancements

  • Allow admin to specify a non-standard location for mksquashfs binary at
    build time with --with-mksquashfs option #1662
  • --nv option will use nvidia-container-cli if installed #1681
  • nvliblist.conf now has a section for binaries #1681
  • --nv can be made default with all action commands in singularity.conf #1681
  • --nv can be controlled by env vars $SINGULARITY_NV and
    $SINGULARITY_NV_OFF #1681
  • Refactored travis build and packaging tests #1601
  • Added build and packaging tests for Debian 8/9 and openSUSE 42.3/15.0 #1713
  • Restore shim init process for proper signal handling and child reaping when
    container is initiated in its own PID namespace #1221
  • Add -i option to image.create to specify the inode ratio. #1759
  • Bind /dev/nvidia* into the container when the --nv flag is used in
    conjuction with the --contain flag #1358
  • Add --no-home option to not mount user $HOME if it is not the $CWD and
    mount home = yes is set. #1761
  • Added support for OAUTH2 Docker registries like Azure Container Registry #1622

Bug fixes

  • Fix 404 when using Arch Linux bootstrap #1731
  • Fix environment variables clearing while starting instances #1766

As always, please report any bugs to:
https://github.com/singularityware/singularity/issues/new

Jul 24, 2018
tagging rc2
Jul 11, 2018
tagging the first release candidate for 2.6.0

@GodloveD GodloveD released this Jul 3, 2018 · 2563 commits to master since this release

Assets 3

Greetings Singularity containerizers!

This release contains fixes for a high severity security issue affecting Singularity 2.3.0 through 2.5.1 on kernels that support overlay file systems (CVE-2018-12021). A malicious user with network access to the host system (e.g. ssh) could exploit this vulnerability to access sensitive information on disk and bypass directory image restrictions like those preventing the root file system from being mounted into the container.

Singularity 2.5.2 should be installed immediately, and all previous versions of Singularity should be removed. The vulnerability addressed in this release affects kernels that support overlayfs. If you are unable to upgrade immediately, you should set enable overlay = no in singularity.conf.

In addition, this release contains a large number of bug fixes. Details follow:

Security related fixes

  • Removed the option to use overlay images with singularity mount. This
    flaw could allow a malicious user accessing the host system to access
    sensitive information when coupled with persistent ext3 overlay.
  • Fixed a race condition that might allow a malicious user to bypass directory
    image restrictions, like mounting the host root filesystem as a container
    image

Bug fixes

  • Fix an error in malloc allocation #1620
  • Honor debug flag when pulling from docker hub #1556
  • Fix a bug with passwd abort #1580
  • Allow user to override singularity.conf "mount home = no" with --home option
    #1496
  • Improve debugging output #1535
  • Fix some bugs in bind mounting #1525
  • Define PR_(S|G)ET_NO_NEW_PRIVS in user space so that these features will
    work with kernels that implement them (like Cray systems) #1506
  • Create /dev/fd and standard streams symlinks in /dev when using minimal dev
    mount or when specifying -c/-C/--contain option #1420
  • Fixed * expansion during app runscript creation #1486

As always, please report any bugs to:
https://github.com/singularityware/singularity/issues/new

Jul 2, 2018
tagging new release candidate
Jun 29, 2018
tagging 2.5.2-rc2
Jun 26, 2018
Tagging release candidate 2.5.2-rc1

@GodloveD GodloveD released this May 3, 2018 · 2563 commits to master since this release

Assets 3

Greetings Singularity community!

This is a bug fix point release to the 2.5 feature branch.

Bug fixes

  • Corrected a permissions error when attempting to run Singularity from a
    directory on NFS with root_squash enabled
  • Fixed a bug that closed a socket early, preventing correct container
    execution on hosts using identity services like SSSD
  • Fixed a regression that broke the debootstrap agent

As always, please report any bugs to:
https://github.com/singularityware/singularity/issues/new