pulling dagger behind a corporate proxy

[upbeat canyon]

Hello,
I'm trying to initialize a dagger module from a corporate network. But it cannot pull the engine but it's blocking

dagger init
✘ connect 0.8s

┃ Error response from daemon: Get "https://registry.dagger.io/v2/": authenticationrequired
Error: new client: failed to pull image: exit status 1

Pulling directly give the same error

docker pull registry.dagger.io/engine:latest
Error response from daemon: Get "https://registry.dagger.io/v2/": authenticationrequired

i can pull image from dockerhub for example.

[rapid thicket]

Hey! Using modules behind corporate environments is not quite fully there given that not only the Dagger Engine but also the module runtime containers should be able to access whtever they need. We're working on shipping that at this specific moment so you should expect an update soon. You can follow this issue for more information: https://github.com/dagger/dagger/issues/6599

Having said that, depending on the type of customization that you need in your environment, you might be able to make it work today. Do you need custom certs to make your corporate proxy work? Or just setting the http_proxy env variable is generally enough?