bug: 401 Unauthorized for private image registries while fetching base image metadata about envd HOT 8 CLOSED

Can you access this private registry locally? This requires your auth file in $HOME/.docker/config.json.

from envd.

Yes, I can. This works when the base image is public but the push address is a private registry.

from envd.

I am not sure if it's related but only thing I can see is that buildkit v0.11.6 has a fix for some 401 Unauthorized issues. https://github.com/moby/buildkit/releases/tag/v0.11.6
moby/buildkit#3779 could we bump up the buildkit version?

from envd.

@mucahitkantepe did you ever verify if this resolved your issue?

I am using the latest (0.3.40) and I get the exact same behavior (it can publish to the private registry, but not use a private base image).

from envd.

@mucahitkantepe did you ever verify if this resolved your issue?

I am using the latest (0.3.40) and I get the exact same behavior (it can publish to the private registry, but not use a private base image).

Yes, it worked for me after the fix

from envd.

Hey @jboutwell-rva were you ever able to get it working? 0.3.45 and I'm still getting this error.. tried dockerhub, ghcr, and ecr. Pushing to a private repo works fine, it's just pulling. I appreciate any help!

from envd.

Hey @jboutwell-rva were you ever able to get it working? 0.3.45 and I'm still getting this error.. tried dockerhub, ghcr, and ecr. Pushing to a private repo works fine, it's just pulling. I appreciate any help!

I ended up working around the issue by using ECR login helper. The trick was the docker config (~/.docker/config.json) was very sensitive to the configuration envd would accept (why envd broke with other valid docker config, I don't know). Here is the exact config I use:

{
	"credsStore": "ecr-login",
	"currentContext": "desktop-linux",
	"credHelpers": {
		"public.ecr.aws": "ecr-login",
		"<account number>.dkr.ecr.us-east-1.amazonaws.com": "ecr-login"
	}
}

from envd.

Awesome, thank you for sharing!

from envd.