login-action/src
breken-ai 53ae646628 use the registry host for the scoped buildx config dir
scopeToConfigDir joined the registry as given onto the Buildx config
dir. For a registry given as a URL this produced
config/https:/<host>/<scope>, and Buildx parses the first path element
as the registry host, so it never finds these credentials.

ECR always hits this: loginECR logs in to the proxy endpoint returned by
GetAuthorizationToken, which is a URL (https://<id>.dkr.ecr.<region>.amazonaws.com),
so a scoped ECR login wrote its credentials to a directory Buildx does
not read, and logout looked in a different directory than login wrote to.

Drop the URL scheme and trailing slashes before building the path.

Assisted-By: Claude
Signed-off-by: breken-ai <312387581+breken-ai@users.noreply.github.com>
2026-09-25 18:50:52 -07:00
..
aws.ts feat: add support for AWS European Sovereign Cloud ECR registries 2026-01-13 16:53:08 +01:00
context.ts use the registry host for the scoped buildx config dir 2026-09-25 18:50:52 -07:00
docker.ts docker hub oidc support 2026-07-22 13:01:46 +02:00
dockerhub.ts log Docker Hub OIDC token exchange progress 2026-08-06 16:51:47 +02:00
main.ts switch to ESM and update config/test wiring 2026-03-01 11:29:31 +01:00
state-helper.ts Add scope input to set scopes for the authentication token 2026-01-13 18:00:29 +01:00