Singularity Global Client
Hi Friends! Are your containers lonely? Singularity containers thrive in happiness when they are shared. This means that wherever you might have them in these cloudy places, they are easy to find and move around.
What is this?
Singularity Global Client is an interface to interact with Singularity containers in many different storage locations. We are able to use modern APIs by way of providing and using the software within a Singularity container! For older architectures, we provide a Singularity container for you to use instead. You can build it from this repository, or use the provided container on Singularity Hub.
If used for the Singularity Registry client, Python 3 is required. See our installation guide to get started. For more details, please refer to our documentation.
Installation instructions
With pip:
pip install sregistry[all]
With conda:
conda install -c conda-forge sregistry
More detailed instructions can be found here
Python Versions Under 3
If you are looking for a version that works with Python 2.* see this branch, or all releases / branches prior to 0.2.0.
Building the RPM
The file sregistry-cli.spec is provided to build an rpm for a specified version, typcailly the current release on pypi, and was discussed here. You should do the following:
- Update the version to be the current in pypi specified in sregistry/version.py.
Version: 0.0.89
- Create a new release on Github with the version spec file added.
- Download the .tar.gz file from the release
VERSION=0.0.92
wget https://github.com/singularityhub/sregistry-cli/archive/sregistry-cli-${VERSION}.tar.gz
- Use rpmbuild to build it.
rpmbuild -ta sregistry-cli-$VERSION.tar.gz
You should get an srpm which that can be distributed and anyone can be rebuilt:
rpmbuild --rebuild sregistry-cli.srpm
License
This code is licensed under the MPL 2.0 LICENSE.
Metadata
Release files for sregistry 0.2.39
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| sregistry-0.2.39.tar.gz | 214.7 kB | Without provenance | Details for sregistry-0.2.39.tar.gz |
Release files / sregistry-0.2.39.tar.gz
| Download URL | sregistry-0.2.39.tar.gz |
|---|---|
| Size | 214.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
db8805e963d34a4fbda329c08d2e913667e01f8ed1511e6597dc8cc4b3ce6d24
|
|
BLAKE2b-256 checksum How to use checksums |
53ba33acb06c5e64c7be28c68e46fa8a303622bf983e38798ef7fb71ee2e51eb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.12
|
Security for sregistry 0.2.39
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.