CHBMB Posted June 12, 2015 Share Posted June 12, 2015 Just my $0.02 I had the dns issue frequently when I also had VMs. Ever since I got rid of the VMs and turned off the VM tab, I never had a single dns issue. I'm using all my containers in bridge mode except for plex and amazon echo which are set to host by default I have always had a mix of VMs and containers and did not experience this issue (not even once) prior to RC6. John I've had it once before, but then never since despite hundreds of reboots.. Both with & without VMs Weird thing is if I'm interpreting sparklyballs' posts correctly then the docker containers actually can ping out to the google DNS server. Link to comment
sparklyballs Posted June 12, 2015 Share Posted June 12, 2015 right, going for a reboot now. Link to comment
eschultz Posted June 12, 2015 Share Posted June 12, 2015 right, going for a reboot now. Here's a even better test: docker exec Sickbeard python -c "import socket; print socket.getaddrinfo('github.com', 80, 0, 0, socket.IPPROTO_TCP)" Link to comment
sparklyballs Posted June 12, 2015 Share Posted June 12, 2015 right, going for a reboot now. Here's a even better test: docker exec Sickbeard python -c "import socket; print socket.getaddrinfo('github.com', 80, 0, 0, socket.IPPROTO_TCP)" Link to comment
sparklyballs Posted June 12, 2015 Share Posted June 12, 2015 root@Unraid-Nas:~# docker exec Sickbeard python -c "import socket; print socket.getaddrinfo('github.com', 80, 0, 0, socket.IPPROTO_TCP)" [(2, 1, 6, '', ('192.30.252.128', 80))] Link to comment
billington.mark Posted June 12, 2015 Share Posted June 12, 2015 Just updated. All my dockers now have this DNS issue (sabnzbd, sickbeard, couchpotato). All are in bridge and all had no issues in rc5. My server is set to have a static IP in the GUI and use my router as DNS, which then uses OpenDNS as its DNS servers. Link to comment
Waseh Posted June 12, 2015 Share Posted June 12, 2015 After updating to rc6 all my dockers disappeared from the docker menu. The docker image is still in place in the docker settings and all my appdata is still there, but no dockers are being reported under the docker tab. I am trying to recreate them from the templates which are still available from the container menu, however im getting at ton of errors trying to start the containers. Just as a heads up. Link to comment
JM2005 Posted June 12, 2015 Share Posted June 12, 2015 After updating to rc6 all my dockers disappeared from the docker menu. The docker image is still in place in the docker settings and all my appdata is still there, but no dockers are being reported under the docker tab. I am trying to recreate them from the templates which are still available from the container menu, however im getting at ton of errors trying to start the containers. Just as a heads up. Did your shares disappear? Link to comment
sparklyballs Posted June 12, 2015 Share Posted June 12, 2015 just to confirm something (and i don't want to lead people down the wrong path) docker exec Readerself python -c "import socket; print socket.getaddrinfo('github.com', 80, 0, 0, socket.IPPROTO_TCP)" exec: "python": executable file not found in $PATH Cannot run exec command d66d8bbe9874064c80f97be1c9d9002aaf4950db5d54b33fc45e63ed57779d0a in container 021569070f15674b1ce3ec23a3d814929a113eaa6beee846e9cf7fce44b6c49b: [8] System error: exec: "python": executable file not found in $PATH Error starting exec command in container d66d8bbe9874064c80f97be1c9d9002aaf4950db5d54b33fc45e63ed57779d0a: Cannot run exec command d66d8bbe9874064c80f97be1c9d9002aaf4950db5d54b33fc45e63ed57779d0a in container 021569070f15674b1ce3ec23a3d814929a113eaa6beee846e9cf7fce44b6c49b: [8] System error: exec: "python": executable file not found in $PATH listening to the cult of mac latest cultcast in readerself. a container that does have connectivity, doesn't have python. Link to comment
CHBMB Posted June 12, 2015 Share Posted June 12, 2015 just to confirm something (and i don't want to lead people down the wrong path) docker exec Readerself python -c "import socket; print socket.getaddrinfo('github.com', 80, 0, 0, socket.IPPROTO_TCP)" exec: "python": executable file not found in $PATH Cannot run exec command d66d8bbe9874064c80f97be1c9d9002aaf4950db5d54b33fc45e63ed57779d0a in container 021569070f15674b1ce3ec23a3d814929a113eaa6beee846e9cf7fce44b6c49b: [8] System error: exec: "python": executable file not found in $PATH Error starting exec command in container d66d8bbe9874064c80f97be1c9d9002aaf4950db5d54b33fc45e63ed57779d0a: Cannot run exec command d66d8bbe9874064c80f97be1c9d9002aaf4950db5d54b33fc45e63ed57779d0a in container 021569070f15674b1ce3ec23a3d814929a113eaa6beee846e9cf7fce44b6c49b: [8] System error: exec: "python": executable file not found in $PATH listening to the cult of mac latest cultcast in readerself. a container that does have connectivity, doesn't have python. Not sure about this one Sparkly, Sonarr I don't think uses python.. Does your RDP-Calibre one have python because was seeing the issue in that as well. Link to comment
johnodon Posted June 12, 2015 Share Posted June 12, 2015 root@unRAID:~# docker exec EmbyServer python -c "import socket; print socket.getaddrinfo('github.com', 80, 0, 0, socket.IPPROTO_TCP)" [(2, 1, 6, '', ('192.30.252.128', 80))] root@unRAID:~# root@unRAID:~# docker exec CouchPotato python -c "import socket; print socket.getaddrinfo('github.com', 80, 0, 0, socket.IPPROTO_TCP)" [(2, 1, 6, '', ('192.30.252.129', 80))] root@unRAID:~# Link to comment
sparklyballs Posted June 12, 2015 Share Posted June 12, 2015 just to confirm something (and i don't want to lead people down the wrong path) docker exec Readerself python -c "import socket; print socket.getaddrinfo('github.com', 80, 0, 0, socket.IPPROTO_TCP)" exec: "python": executable file not found in $PATH Cannot run exec command d66d8bbe9874064c80f97be1c9d9002aaf4950db5d54b33fc45e63ed57779d0a in container 021569070f15674b1ce3ec23a3d814929a113eaa6beee846e9cf7fce44b6c49b: [8] System error: exec: "python": executable file not found in $PATH Error starting exec command in container d66d8bbe9874064c80f97be1c9d9002aaf4950db5d54b33fc45e63ed57779d0a: Cannot run exec command d66d8bbe9874064c80f97be1c9d9002aaf4950db5d54b33fc45e63ed57779d0a in container 021569070f15674b1ce3ec23a3d814929a113eaa6beee846e9cf7fce44b6c49b: [8] System error: exec: "python": executable file not found in $PATH listening to the cult of mac latest cultcast in readerself. a container that does have connectivity, doesn't have python. Not sure about this one Sparkly, Sonarr I don't think uses python.. Does your RDP-Calibre one have python because was seeing the issue in that as well. don't have it installed at the moment. Link to comment
Waseh Posted June 12, 2015 Share Posted June 12, 2015 After updating to rc6 all my dockers disappeared from the docker menu. The docker image is still in place in the docker settings and all my appdata is still there, but no dockers are being reported under the docker tab. I am trying to recreate them from the templates which are still available from the container menu, however im getting at ton of errors trying to start the containers. Just as a heads up. Did your shares disappear? No only difference is all dockers are gone - Shares and everything else (plugins etc.) are working as before the update. Not quite sure what is going on. Link to comment
CHBMB Posted June 12, 2015 Share Posted June 12, 2015 After updating to rc6 all my dockers disappeared from the docker menu. The docker image is still in place in the docker settings and all my appdata is still there, but no dockers are being reported under the docker tab. I am trying to recreate them from the templates which are still available from the container menu, however im getting at ton of errors trying to start the containers. Just as a heads up. Did your shares disappear? No only difference is all dockers are gone - Shares and everything else (plugins etc.) are working as before the update. Not quite sure what is going on. Where is your docker.img located? Is that still there and on a cache only share? Link to comment
CHBMB Posted June 12, 2015 Share Posted June 12, 2015 Similar result for my Sonarr docker: root@unRAID:~# docker exec Sonarr python -c "import socket; print socket.getaddrinfo('github.com', 80, 0, 0, socket.IPPROTO_TCP)" exec: "python": executable file not found in $PATH Cannot run exec command 4f7b7bbfa6ecb4e12dd1d58c28ce17936489054358e8b212deadf9f0b051b924 in container a8c48c404d251beb03900ffe60b3913195d621fa2625945eaa4e68ba1eac348a: [8] System error: exec: "python": executable file not found in $PATH Error starting exec command in container 4f7b7bbfa6ecb4e12dd1d58c28ce17936489054358e8b212deadf9f0b051b924: Cannot run exec command 4f7b7bbfa6ecb4e12dd1d58c28ce17936489054358e8b212deadf9f0b051b924 in container a8c48c404d251beb03900ffe60b3913195d621fa2625945eaa4e68ba1eac348a: [8] System error: exec: "python": executable file not found in $PATH root@unRAID:~# That reads to me that python isn't present in the Sonarr container, which would go against Sparklys' theory... Link to comment
JM2005 Posted June 12, 2015 Share Posted June 12, 2015 After updating to rc6 all my dockers disappeared from the docker menu. The docker image is still in place in the docker settings and all my appdata is still there, but no dockers are being reported under the docker tab. I am trying to recreate them from the templates which are still available from the container menu, however im getting at ton of errors trying to start the containers. Just as a heads up. Did your shares disappear? No only difference is all dockers are gone - Shares and everything else (plugins etc.) are working as before the update. Not quite sure what is going on. The reason I asked was that i tried to update from rc4 to rc5 yesterday and my shares disappeared and some of my dockers would not start. I have not tried rc6 yet as I rolled back to rc4 and all is fine. My shares are on my cache drive. Link to comment
HellDiverUK Posted June 12, 2015 Share Posted June 12, 2015 Everything is still working OK for me (Sonarr, Couchpotato, Deluge, NZBGet, Plex) post update to RC6. No issues to report. Docker and appdata is on the cache drive. Link to comment
sparklyballs Posted June 12, 2015 Share Posted June 12, 2015 Similar result for my Sonarr docker: root@unRAID:~# docker exec Sonarr python -c "import socket; print socket.getaddrinfo('github.com', 80, 0, 0, socket.IPPROTO_TCP)" exec: "python": executable file not found in $PATH Cannot run exec command 4f7b7bbfa6ecb4e12dd1d58c28ce17936489054358e8b212deadf9f0b051b924 in container a8c48c404d251beb03900ffe60b3913195d621fa2625945eaa4e68ba1eac348a: [8] System error: exec: "python": executable file not found in $PATH Error starting exec command in container 4f7b7bbfa6ecb4e12dd1d58c28ce17936489054358e8b212deadf9f0b051b924: Cannot run exec command 4f7b7bbfa6ecb4e12dd1d58c28ce17936489054358e8b212deadf9f0b051b924 in container a8c48c404d251beb03900ffe60b3913195d621fa2625945eaa4e68ba1eac348a: [8] System error: exec: "python": executable file not found in $PATH root@unRAID:~# That reads to me that python isn't present in the Sonarr container, which would go against Sparklys' theory... i do have another theory though. my containers that aren't connecting have "check for update" at start in one form or another.... deluge doesn't Link to comment
johnodon Posted June 12, 2015 Share Posted June 12, 2015 Going to remove my post RE: Sonarr and the command Eric asked us to run as it has nothing to do with the DNS issue. Link to comment
sparklyballs Posted June 12, 2015 Share Posted June 12, 2015 just to confirm something (and i don't want to lead people down the wrong path) docker exec Readerself python -c "import socket; print socket.getaddrinfo('github.com', 80, 0, 0, socket.IPPROTO_TCP)" exec: "python": executable file not found in $PATH Cannot run exec command d66d8bbe9874064c80f97be1c9d9002aaf4950db5d54b33fc45e63ed57779d0a in container 021569070f15674b1ce3ec23a3d814929a113eaa6beee846e9cf7fce44b6c49b: [8] System error: exec: "python": executable file not found in $PATH Error starting exec command in container d66d8bbe9874064c80f97be1c9d9002aaf4950db5d54b33fc45e63ed57779d0a: Cannot run exec command d66d8bbe9874064c80f97be1c9d9002aaf4950db5d54b33fc45e63ed57779d0a in container 021569070f15674b1ce3ec23a3d814929a113eaa6beee846e9cf7fce44b6c49b: [8] System error: exec: "python": executable file not found in $PATH listening to the cult of mac latest cultcast in readerself. a container that does have connectivity, doesn't have python. Not sure about this one Sparkly, Sonarr I don't think uses python.. Does your RDP-Calibre one have python because was seeing the issue in that as well. the rdp image has python. Link to comment
CHBMB Posted June 12, 2015 Share Posted June 12, 2015 just to confirm something (and i don't want to lead people down the wrong path) docker exec Readerself python -c "import socket; print socket.getaddrinfo('github.com', 80, 0, 0, socket.IPPROTO_TCP)" exec: "python": executable file not found in $PATH Cannot run exec command d66d8bbe9874064c80f97be1c9d9002aaf4950db5d54b33fc45e63ed57779d0a in container 021569070f15674b1ce3ec23a3d814929a113eaa6beee846e9cf7fce44b6c49b: [8] System error: exec: "python": executable file not found in $PATH Error starting exec command in container d66d8bbe9874064c80f97be1c9d9002aaf4950db5d54b33fc45e63ed57779d0a: Cannot run exec command d66d8bbe9874064c80f97be1c9d9002aaf4950db5d54b33fc45e63ed57779d0a in container 021569070f15674b1ce3ec23a3d814929a113eaa6beee846e9cf7fce44b6c49b: [8] System error: exec: "python": executable file not found in $PATH listening to the cult of mac latest cultcast in readerself. a container that does have connectivity, doesn't have python. Not sure about this one Sparkly, Sonarr I don't think uses python.. Does your RDP-Calibre one have python because was seeing the issue in that as well. the rdp image has python. Still doesn't explain Sonarr.. Link to comment
bondoo0 Posted June 12, 2015 Share Posted June 12, 2015 Same DNS issue as others, was fine in RC5. Also static IP for unraid. Using VMs and docker. Seeing the issue with Sonarr, CP, and Emby. I didn't see the issue with SABnzbd (or it was fixed when I saved the other dockers). Link to comment
CHBMB Posted June 12, 2015 Share Posted June 12, 2015 Well I'm systematically finding the issue on all my containers, pretty sure Plex as well, and that uses host networking... I'm finding if I edit then save a container that restores connectivity for me. Going through them all and then going to try a reboot. Link to comment
bondoo0 Posted June 12, 2015 Share Posted June 12, 2015 Well I'm systematically finding the issue on all my containers, pretty sure Plex as well, and that uses host networking... I'm finding if I edit then save a container that restores connectivity for me. Going through them all and then going to try a reboot. Same thing, if I do a save on the container (even with no changes) it rebuilds the container and fixes the issue. Link to comment
binhex Posted June 12, 2015 Share Posted June 12, 2015 I've seen the DNS issue with a Java application, so I don't believe it's linked to the presence of Python Link to comment
Recommended Posts