docker build error cannot connect
When docker build suddenly stopped working saying, "The remote name could not be resolved", I wasted alot of time trying many things to bring it back online. In this quick demo I show the fix and offer a couple of useful tips that I hope saves people time :)
00:00 Intro
00:09 What error? "The remote name could not be resolved"
00:25 Simplify the problem first
00:48 Problem occurred on a Windows machine running Windows containers
01:00 A few things I tried
01:27 Grab the error and give it to copilot
01:39 Don't fall into the trap of "I didn't need that before, so I won't try that..."
01:59 Add dns array to demon.json
02:35 Use net stop and start to restart docker
02:50 Did that help? No because the change wasn't picked up using the command to restart
03:10 Restart from Docker Desktop
03:27 Did that work? Again no, because restarting from Docker Desktop causes the manual change to daemon.json to be lost
03:42 Add the dns settings via Docker Desktop UI
04:09 Does docker build work now? Yes :)
On this page of the site you can watch the video online docker build error cannot connect with a duration of hours minute second in good quality, which was uploaded by the user SprintDeployLearnRepeat 13 February 2025, share the link with friends and acquaintances, this video has already been watched 137 times on youtube and it was liked by 2 viewers. Enjoy your viewing!
