DNS Issues in Engine after Upgrade

[lethal sail]

I ran into this issue a few weeks ago while working at WeWork. I thought that it was something to do with the WeWork network but now I am thinking that it has to do with the Docker network.

Everything was working fine, but after upgrading the engine I was no longer able to run any functions because Dagger failed to install my modules because it could not connect to the golang proxy

github.com/google/go-cmp/cmp/cmpopts: github.com/distribution/reference@v0.6.0: Get "https://proxy.golang.org/github.com/distribution/reference/@v/v0.6.0.mod": dial tcp: lookup proxy.golang.org on 10.87.0.1:53: read udp 10.87.0.16:41320->10.87.0.1:53: i/o timeout

I was able to resolve this by restarting my docker engine.

sudo systemctl restart docker

I am still not 100% sure that this has anything to do with Dagger but I wanted to document this here in case anyone else runs into this issue.

[steep cosmos]

Hey Lev! I'm quite sure it's not Dagger related. I experienced similar issues in the past with Docker while switching networks and/or using a VPN. It has also been brought up a while ago in Discord as well. Not much we can do in our end about this one unfortunately.