mr9v9 Posted November 11, 2018 Share #1 Posted November 11, 2018 (edited) Has anyone experience UNC path problems to their NAS when running a Docker container? When not in use I can browse to my Diskstation shares on Windows using \\MYNAS just fine. When Docker containers run I can only use \\192.x.x.x on certain devices. Might even be a Windows 10 thing. I can touch my containers files with forward mapped ports to get to them on my local subnet no problem. Docker is set to use the 172.x.x.x subnet and I run containers in bridged network mode. Is there some sort of conflict with the way the Docker container is running? Or is this a bug with Windows 10? Edited November 11, 2018 by mr9v9 Quote Link to comment Share on other sites More sharing options...
ideasman69 Posted November 11, 2018 Share #2 Posted November 11, 2018 when you ping mynas from the command prompt - what does it come back with? Quote Link to comment Share on other sites More sharing options...
mr9v9 Posted November 11, 2018 Author Share #3 Posted November 11, 2018 3 minutes ago, ideasman69 said: when you ping mynas from the command prompt - what does it come back with? It pings 172.17.0.1 and request times out. Which means it can't cross the subnet unless I change my ip to match. Quote Link to comment Share on other sites More sharing options...
ideasman69 Posted November 11, 2018 Share #4 Posted November 11, 2018 thats pretty weird. it's like one of the docker containers you're running is updating the DNS name for mynas to its internal docker IP. can you try turning them all off and turn them on one by one to see if it's all of them - or just 1? Quote Link to comment Share on other sites More sharing options...
mr9v9 Posted November 11, 2018 Author Share #5 Posted November 11, 2018 I think the culprit is Emby, but it gets very strange because it happens when no containers are running. If I stop Docker manually and try pinging again same problem. ipconfig tools with /release /renew /flushdns do nothing, as well as rebooting my PC. Quote Link to comment Share on other sites More sharing options...
ideasman69 Posted November 12, 2018 Share #6 Posted November 12, 2018 running those ipconfig commands will just re-grab the dns entry for mynas from your dns server (more than likely your router). You need to get your synology to re-register it's ip in DNS (rebooting or using dhclient command). if you use nslookup mynas it should tell you what IP your DNS server has for that hostname. as for emby - maybe don't use bridged network for this docker? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.