Networking errors after calling `Sync()`... | Dagger | Page 1

earnest stag Jan 31, 2024, 4:13 AM

#

I am not doing a sync() though. Does the CLI automatically do a sync?

brittle trail Jan 31, 2024, 4:14 AM

#

Sync is only one way to hit that problem, it's more general than that. I am admittedly just going off lookup 6lrxqnijxx4lg on 10.*.*.*:53: no such host being the same error, so I can't be sure it's the exact same problem, but seems likely

earnest stag Jan 31, 2024, 4:16 AM

#

hmm, yeah it's possible. Not doing anything fancy, just returning the *Container from the function and then calling it from the CLI.

earnest stag Jan 31, 2024, 9:47 PM

#

Follow up, I was able to resolve this with help from @cinder tree . Thank you Kyle! Apparently my docker-in-docker image (dind) proxied via my company registry had an old version of it cached. So it didn't have the correct ip_tables version and it borked. Figured this out by enabling debug logging for the dockerd. After force pulling docker:24.0-dind the issue went away. So, the issue was not related to dagger in the end. Since I wasn't juggling multiple services or using sync() it wasn't related to https://github.com/dagger/dagger/issues/6493 even though the error message was the same.

brittle trail Jan 31, 2024, 9:51 PM

#

earnest stag Follow up, I was able to resolve this with help from <@135620352201064448> . Tha...

Great to hear, sorry for bucketing it into that other issue too quickly, and thank you @cinder tree for digging into it!

#Networking errors after calling `Sync()`...