Community Call - 3rd August (Cancelled) #1962
                  
                    
                      dtrudg
                    
                  
                
                  announced in
                Community Call
              
            Replies: 0 comments
  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment
  
        
    
Uh oh!
There was an error while loading. Please reload this page.
-
Due to August being a month of holidays for many, we've decided to cancel the 3rd August SingularityCE Community Call.
Below is a brief update of development progress. We hope to see you on Thursday 7th September, where we expect to be demonstrating the new features of the SingularityCE 4.0.0 release candidate.
Please don't hesitate to discuss any development topics here, on Google Groups, or in the SingularityCE Slack workspace.
August Development Update
Rework of
remotecommandThe
singularity remotecommand has been overloaded for some time, causing confusion.For 4.0.0 @preminger has been working to split credentials mangement for OCI registries into a new
singularity registrycommand, and standalone keyserver management into a newsingularity keyservercommand.The
singularity remotecommand is now dedicated to the management of SCS (cloud.sylabs.io) and Singularity Enterprise, or compatible, remote endpoints only. Output of thelistsubcommand has also been tidied up.--ociModeThe SingularityCE compilation process now builds and bundles a modern version of
squashfuse, to avoid issues running SIF containers on distributions that provide an older versions. Multithreadedsquashfuse_llis preferred.OCI-SIF images are automatically detected, so that the
oci-sifprefix is not needed to run them.OCI-SIF images can now be pushed and pulled to/from
library://anddocker://URIs, as OCI images with a single squashfs layer. They can also be pushed to OCI registries as a single file, usingoras://.Developer Related
The
go.modforgithub.com/sylabs/singularitywill soon declare itself asv4module, to match the application version of SingularityCE.The location of code, whether in
pkg/orinternal/pkghas been reviewed with the aim of following semantic versioning, as expected for go modules, fromv4.Push/pull to
oras://has been rewritten, to remove theoras-go/v1dependency that has delayed other dependency updates in the past. Through SingularityCE 4.x we expect to additionally move fromcontainers/imagetogoogle/go-containerregistryfor OCI image handling. This will considerably reduce the number of go module dependencies that SingularityCE requires.Release Candidate Progress
We hope to issue a 4.0.0 release candidate on or around 17th August.
Check the 4.0.0 GitHub milestone to monitor progress on the remaining work: https://github.com/sylabs/singularity/milestone/4
Beta Was this translation helpful? Give feedback.
All reactions