@some-cricket-23089 This might be a longshot but can you tell what ip range your machine is on for its private internal address? How you do so will depend on your OS so if you can't figure it out, let me know your OS. One thing I've had happen a few times to me is that docker defaults to using the

172.17.0.0/16

subnet and if your work's network (I'm assuming you're in office, but perhaps not) uses the same subnet for their internal networking (like my company did), then containers can break being able to reach the net. Now if OTHER steps in the build are able to execute and download things just not from Cypress -- I'm not sure but will keep thinking on it. For some debugging, share the output of this:

docker network ls

and

docker network inspect bridge

This may not be the issue, I just want to eliminate ip conflicts as the source of not being able to reach out as I've had that happen to me twice with other projects.