#Running Dagger inside closed network

1 messages · Page 1 of 1 (latest)

slender kite
#

I have created a dagger module with dagger init python sdk, a simple pipeline setup inside a private network. There is a private docker registry and private git etc in the network. When I try listing functions with dagger functions the command timed out pulling some images from docker.io, how can i force dagger to use internal python images for example? thank you

burnt plaza
#

Hey @slender kite! Is your private registry working as a mirror for docker.io internally?

slender kite
#

Pull, re-tag and push

#

Maybe you can tell me which tags of images are being used for dagger commands and how do I force dagger to use internal registry tag that contains the same thing

#

Also how to make dagger trust the registry ssl connection

violet dragon
#

unfortunately there's no straightforward way currently to run Dagger in an exclusive (air-gapped) private network at this moment. It's not something that we can guarantee since we haven't specifically added support for it.

The place to continue this conversation should be: https://github.com/dagger/dagger/issues/5913

GitHub

Some users hit roadblocks when the dagger engine has hard dependencies on pulling e.g. container images from dockerhub or other resources from the internet at runtime. This is typically due to stri...

burnt plaza
burnt plaza
#

Re-reading your message, I see that you are talking about a completely closed off network. In that case, even if you configure mirrors it won't work. There's other things that dagger needs to fetch that are not just images from registries. Like @violet dragon said we don't yet have support for running dagger in those kinds of environments

slender kite
#

This is very unfortunate. My team will be dropping dagger for now. Thank you for the explanation and fast response 😁