Dave Trudgian

We've shuffled this issue around on & off milestones now, because we have a few concerns about how complete and consistent this type of feature could be, if added to...

Hi @gregseth - thanks for the report. This is actually a known issue that should have already been filed by ourselves. Unfortunately it's a bit more complex to address than...

This is rather involved due to our environment setup withing the container being performed by a shell interpreter running the action script, which in turn will source other scripts in...

> Expected behavior print a warning that authentication failed, retry anonymously. Not sure that we want to do this. I am of the opinion that if credentials have been set...

@vsoch - this is not the case for docker, podman etc. though - which I believe are the best targets to emulate here w.r.t. interaction with OCI registries. With docker,...

> Sorry it's the other way around - you try without _any token_ first, and only add the token to try on that failure. Right - that's what we don't...

We are calling out to other 3rd party packages to actually do our operations against OCI registries, and that might be where an `always auth first if configured` vs `noauth...

@myoung3 > Additional context it would also be good if there was a way to remove authenticated logins Try `singularity remote logout ....` - I forgout about that one for...

> Don't know how I missed that! But after doing `singularity remote logout oras://ghcr.io` the URI "oras://ghcr.io" seems to persist in the output of `singularity remote`. Perhaps the issue is...

> At least I think #214 should help since logging out should work now, but I think not being able to pull public packages due to an invalid PAK is...