Now that we have readied the WSL2 environment with Singularity and the relevant CUDA libraries, it’s time to run the sample Keras workflow.
Greetings to the Singularity community. My name is Jason Tuschen and I have been the CEO of Sylabs since April of 2020. Prior to that, I had a 27-year career in the Navy and started a small consulting firm.
I am humbled to be part of a team and community that directly contributes to the betterment of the world.
One lesson that has rung true over my years leading teams around the globe in the most challenging of environments is that transparency, open communication and collaboration are always a recipe for success. That is just as critical to an open-source community like Singularity as it is to the SEAL Teams.
Since transferring the repositories to HPCng in May of 2020, Sylabs has remained a key contributor to the project but has not been involved in the HPCng board or management. HPCng has a much broader scope than Singularity. While we have no doubts that they will succeed in their multiple endeavors and look forward to seeing what they achieve, our primary sights have been and will remain focused on Singularity.
This decision to fork simply boils down to a philosophical difference of opinion on how the project should be led. Our decision to fork was not one that was made in a vacuum and a thorough risk assessment was conducted internally. When two entities are equally as passionate about something but see things differently, it has the potential to cause unnecessary tension, toxicity or collateral damage. We feel that in the long run, it is in everyone’s best interest if we proceed down this road. Ultimately, we firmly believe that this change poses less of a risk to the project long term than the risk of the status quo.
Any transition regardless of how big or small, can be disruptive. We firmly believe that transparency and open dialogue mitigate that disruption. It is our sincere hope that the entire community embrace that open dialogue and freely communicate among each other to ensure the best outcome for Singularity.
Please reach out and join our community. Our new Slack workspace for this fork has been established at: SingularityCE Slack
A new mailing list / Google Group for this fork has been established at: https://groups.google.com/g/singularity-ce
GitHub repositories: https://github.com/sylabs
As I said in the beginning, I am humbled to be a part of this community and helping contribute in some small way to amazing work done by all of you.
All the best,
Join Our Mailing List
Signing the Container The Singularity 3.0 family introduced the ability to create (and manage) PGP keys to sign and verify containers. This provides a trusted method for Singularity users to share containers and ensures a bit-for-bit reproduction of the original...
Create an Account & Authentication Token Now that we have SingularityCE installed in WSL2, and NVIDIA GPU support is enabled, we will create a Singularity Container Services account and configure the local Singularity client, followed by building a remote...