Jake Sanders

There's also precedent for defining certs using flags on the Docker client: https://docs.docker.com/engine/reference/commandline/cli/

@mattmoor [looks like it,](https://docs.docker.com/engine/security/https) yeah. Seems like `/etc/docker/certs.d/...` is for daemon registry communications

I'm currently in Copenhagen (taking some vacation after DockerCon), but I believe the issue may be that ~/.docker/config.json needs to be in a volume which is shared between docker-credential-gcr, docker-compose,...

Ok. I'll look into it in more depth when I'm back home (next week). Until then, you could try removing docker-credential-gcr from your docker config, setting an environment variable like...

I did, but for now it's only supported for remote -> remote registry transfers, which allows for `gcloud container images add-tag` to work with windows containers. More work will be...

The issue is that `docker` doesn't supply any parameters to `docker-credential-gcr` via the credential store API. However, you should be able to use the `DOCKER_CONFIG` ENV var to specify the...

Got it. FYI only the config directory is user-configurable, [`config.json` is hard-coded](https://github.com/GoogleCloudPlatform/docker-credential-gcr/blob/7daa5a7d01642853e49ca30d96e79704355b1f2e/vendor/github.com/docker/cli/cli/config/config.go#L19).

GCR's most requested features can't naturally be implemented on top of GCS. For that reason, GCR most likely will not be expanding our feature parity with it. (Sorry, this is...

ARM64 is included in the latest release: https://github.com/GoogleCloudPlatform/docker-credential-gcr/releases/tag/v2.0.0

It appears that the example implementation given uses a dedicated `community` repo to serve as the source-of-truth and record of updates to the community spec. Should a `https://github.com/slsa-framework/community` repo be...