#👋🏼

1 messages · Page 1 of 1 (latest)

tepid lake
#

well, technically should be public, but I am getting an error also in my host, so maybe not related to Dagger itself.

#

I think I found the issue, it seems that my module was loading the credentials from the host, without me knowing, and I had wrong credentials in my .docker/config

#

cc/ @wooden lance since I asked in another thread

#

so basically although I was pulling a public image, dag.Container.From was taking credentials from the host.

FWIW this was unexpected

#

can I make sure in my module that this never happens again? I tried WithoutRegistryAuth but didn't seem to work or I don't know how to use it

raven glacier
#

I personally like the convenience of being able to docker login on my host. Otherwise, we'd need a custom dagger engine image that has the auth. But I understand your need also, it would be nice to be able to tell the engine not to pull host creds in certain scenarios.

tepid lake
#

Yes, me too, but as you said, a way to say please don't authenticate would be nice to prevent this kind of issue. That I have credentials that are not valid in my host and didn't notice

wooden lance
#

Yeah that request makes sense! I'll write an issue