fix(runner): encode registry auth with padding the daemon can decode #20
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/registry-auth-padding"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
RegistryAuth encoded X-Registry-Auth as unpadded base64url, but the
daemon decodes it with registry.DecodeAuthConfig, which requires
padding. Whenever the credential JSON length was not a multiple of
three, decoding failed; the daemon drops that error and pulls
anonymously, so the private studioteal-private/gbb-macos image failed
with "unauthorized: reqPackageAccess" despite a valid token.
Use registry.EncodeAuthConfig, the daemon decoder's counterpart, and
test the round trip through DecodeAuthConfig across JSON lengths.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com