Releases: GoogleCloudPlatform/docker-credential-gcr
v1.4.3 w/ static binaries
Strong, independent binaries who don't need no distro.
Prune GCR registries
This release prunes the number of GCR registries down to the minimum set necessary to fully authenticate all requests. The end result is faster docker builds
for older clients.
k8s.gcr.io authentication, various improvements
- Authenticates
k8s.gcr.io
rather thangcr.kubernetes.io
. Please rundocker-credential-gcr configure-docker
to pick up this change in thedocker
client. - Refreshes
gcloud
's access token when fetching it.
Bug fixes, disable bucket registry
- Fix an issue which would cause an error with the
list
surface which affecteddocker build
. - Stop authenticating for b., bucket. and beta.gcr.io registries by default.
Container Optimized OS, 6/5/2017 release
1.4.0 -> 1.4.1 Change-Id: I5af2a39fbb7eb9b373bf3bb54a274ca8d5769bdc Signed-off-by: Jake Sanders <jsand@google.com>
Container-Optimized OS release
This release is to give GKE's Container-Optimized OS a stable branch to pull against.
1.4.0 release
v1.3.5 added:
- Updates the command used to retrieve the gcloud SDK's access token to
gcloud config config-helper --format=value(credential.access_token)
v1.4.0 added:
- When --configure-docker cannot determine the installed version of the Docker client (e.g. if the Docker client isn't installed yet), the credential helper now assumes that it can configure itself to be a registry-specific credential helper.
Support new Docker client version numbering
--default-to-gcr-access-token
--default-to-gcr-access-token has been added as a config
value. By default, the credential helper will still return an error when an unknown credential is requested, but when --default-to-gcr-access-token is enabled the credential helper will attempt to return GCR's access token instead. This allows for the credential helper to be used for non-default GCR registries.
Bugfix!
Some users were having issues using configure-docker, which is solved in this bugfix.