-
-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sregistry with sif images on Gitlab api/v4 #351
Comments
Are you using Singularity Registry server, or the sregistry client (which is at https:/singularityhub/sregistry-cli). They are different. You should look at the gitlab section in there and open a PR if there is a bug. And if [4] works, why not just use that? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I have attached sregistry to our local gitlab instance and can browse my build artifacts [1]. However, pulling an image file from the artifacts fails with [2].
As far as I see, the problem is, that the clients tries to read a *.simg, while I had been building *sif's with Singularity 3. I already tried to change the name accordingly [3] but without success. Requesting the file works in principle [4].
Unfortunately, I did not find the API definitions, so that I could try to patch the request.
Cheers and thanks,
Thomas
[1]
[2]
[3]
[4]
curl -L -s --header "PRIVATE-TOKEN: ${SREGISTRY_GITLAB_TOKEN}" "https://gitlab.desy.de/api/v4/projects/588/jobs/14300/artifacts/build/Singularity.sif" -o /tmp/foo.sif
The text was updated successfully, but these errors were encountered: