I got rated limited again 😞

[broken salmon]

This is even with doing a docker login on your machine I'm guessing?

just double checking because the engine does pick up your ~/.docker creds

[cold prism]

I'm pretty sure it's picking up my credentials, since it shows my username in the error message: You have reached your pull rate limit as 'alexcb132'

unfortunately I haven't been able to reproduce the bug I'm chasing down via an integration test, so i've just been building dagger constantly.

[broken salmon]

Yeah I guess unless you pay dockerhub you only get 100/h...

You can tell the engine to use a mirror: https://docs.dagger.io/reference/configuration/engine/#custom-registries

Would require some tedious-ish setup but you could get it to work

[polar breach]

cc @toxic cedar @dire summit @rapid kernel do we have a team docker org to work around this, and if so: can we share it with @cold prism ?

[broken salmon]

I shared my personal creds w/ him privately to unblock him, but yeah if we have a paid team org even better

[rapid kernel]

I'm not aware of any team account if we have one!

I think we have a few :latest tags scattered around, so maybe we can replace those with a major tag or something to reduce the amount of pulls

[cold prism]

I managed to setup a pull through cache, so I'm hoping that helps reduce the number of pulls too, but it's not completely obvious if it's working or not (docker exec dagger-engine.dev sh -c 'cat /etc/dagger/engine.toml' does show that the configs have made their way to the engine)

[dire summit]

when using pull through cache IIRC the engine logs should say something while trying to pull the image

checking if there are any docker creds in 1p now 🙏

found the account. Creds sent via DM

[polar breach]

@dire summit could you send me the creds also? 🙏