Skip to content
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

Adding ACR as a remote (docs) #308

Open
radoye opened this issue Aug 8, 2019 · 1 comment
Open

Adding ACR as a remote (docs) #308

radoye opened this issue Aug 8, 2019 · 1 comment
Assignees

Comments

@radoye
Copy link

radoye commented Aug 8, 2019

Version of Singularity:

3.2.0-1

Expected behavior

An example of how to properly add an ACR as a remote?

singularity remote add devhub <my registry>.azurecr.io
singularity remote login devhub 
singularity push xyz.sif devhub

Actual behavior

It's unclear to me what should go into the remote command. Simply putting the Azure supplied "login server" string (.azurecr.io) in does not make Singularity client happy.

Steps to reproduce behavior

singularity push dev.sif oras://<my registry>.azurecr.io/dev:0.1.1
FATAL:   Couldn't push image to library: no authentication token, log in with 'singularity remote` commands
@dtrudg
Copy link
Contributor

dtrudg commented Feb 10, 2020

The remote command is exclusively for Sylabs cloud services, i.e. the container library library:// URLs, remote builder, key store.

ORAS support was only added in 3.3.0 - the older 3.2.0 here is incorrectly trying to interpret the oras:// URI as if it was a library one.

We do need some oras docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants