Jon Johnson

I'd say this is mostly an issue with docker. I believe (@dekkagaijin can correct me if I'm wrong) that docker will fetch all credentials for all registries in your config...

> The arguments passed to the tool are as follows: > `--name docker.io/libarary/ubuntu:latest --tarball /tmp/ubuntu.tar` This looks like a typo: libarary -> library

My recollection might be fuzzy here, but I believe we originally distributed `docker-credential-gcr` through gcloud prior to the `docker-credential-gcloud` credential helper's existence. Given that you can just use gcloud for...

@astleychen on COS specifically? This might be what's going on: https://stackoverflow.com/questions/51236449

Technically, yes, but unfortunately not in a way that's useful to you. The test suite uses a bunch of google-internal stuff, so the tests get stripped as part of the...

I think this is also caused by `credSstore` being incorrectly capitalized, i.e. not `credsStore`... are you still hitting this? It wouldn't be too hard to check both keys.

Assuming you're using gcloud and not a JSON key or environment-based auth, `gcloud auth list` should show you the current active account. The auth attribute value in the config file...

I don't think this repo is the right place for this issue, you probably want skopeo?

@mjgallag I generally agree with you and share in your frustrations here. > One would like to be able to manage image lifecycle via Docker Registry HTTP API V2 which...

> Since it is internal I'd like to find a way to easily identify and delete unused images, i.e. garbage collection. If I can't find a flow that works with...