You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For ACR and Dockerhub, the authConfigs map does need the https:// prefix for lookup.
A side note: I am fairly certain most users would pass in the registry username and password/token-as-password directly from creating the registry inline in the program.
This appears to be a subtle difference in the credential helpers used to call GetAllCredentials between either OSes or docker engine versions.
Solution to move forward: Try both lookups in authConfig.
guineveresaenger
changed the title
Pushing to ECR requires errors due to "https://" prefix on push config
"https://" prefix on push config is required on some systems and not on others
Feb 2, 2023
I found that when using ECR login using the credential tool, I received a confusing error message: "no basic auth credentials".
Steps to reproduce
aws ecr get-login-password
.This created an authconfig entry in docker/config.json for
[registry hostname]
withouthttps://
.Expected behavior
Successful push.
Actual behavior
Error "no basic auth credentials".
Root causing
The
registryServer
on line 210 here began withhttps://
, but theauthConfigs
map contained only hostnames withouthttps://
:pulumi-docker/provider/image.go
Lines 210 to 216 in f41fbf4
The text was updated successfully, but these errors were encountered: