Topic says it all. When I use the apt based Docker I can edit the daemon.json to include my Dnsmasq and all is well in the world. However when using the Snapd version I'm not sure how to do it. I cannot add my http_proxy via fqdn.
Code:
docker build -t foo --build-arg http_proxy=http://proxy.mylan.home:3129/ .
fails while
Code:
docker build -t foo --build-arg http_proxy=http://192.168.1.2:3129/ .
works flawlessly. In migrating my services I've also found that they don't resolve my dns. In the case of a headless Kodi I recently built to manage the libraries I cannot use rather I need to use I'm not sure why this is. I've had little success searching for how to accomplish this. Typically typing anything involving Docker + snap results in how to install the snapd version. I've opened up my dnsmasq to accept from the Docker ip range but I can't seem to make Docker target it specifically.
Bookmarks