June 12, 201511 yr 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. I think Tom had mentioned this in another post.
June 12, 201511 yr I've seen the DNS issue with a Java application, so I don't believe it's linked to the presence of Python it was a theory based on my installed apps, it was the only common thing i could see between apps that were failing to connect and those that weren't.
June 12, 201511 yr Can confirm that editing then saving the docker apps resolves the DNS issue. everything resolving as it should from the docker images now. Maybe add this to the OP as a known issue and workaround?
June 12, 201511 yr I think Tom had mentioned this in another post. Yeah I remember doing it on one of the earlier betas or RCs, just hope it survives a reboot. Right pain in the hole.
June 12, 201511 yr 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? On a drive outside the array - I have since deleted the docker image and recreated it and now i can recreate the containers from the templates without errors. No idea what happened but it seems to be working again now.
June 12, 201511 yr 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. I think Tom had mentioned this in another post. Confirmed. I Edited my Emby container, clicked Save and DNS appears to be working. John
June 12, 201511 yr 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. I have always run my Plex in host mode and I have issues with metadata often (that is grabbing media covers etc.), a rebuild of the Docker always fixes it.
June 12, 201511 yr I think Tom had mentioned this in another post. Yeah I remember doing it on one of the earlier betas or RCs, just hope it survives a reboot. Right pain in the hole. Didn't survive a reboot... I'm rolling back to RC5, sure hope this isn't going to end up as the final release.
June 12, 201511 yr i just added this to extra parameters in a container that doesn't connect and it's connected after one reboot so far, not exactly rigorous testing i know... --dns 8.8.8.8
June 12, 201511 yr I'm still having trouble updating. I'm on rc4, but checking for plugin updates still says unRAID is up-to-date. Do plugins impact whether you see an unRAID update?
June 12, 201511 yr I'm still having trouble updating. I'm on rc4, but checking for plugin updates still says unRAID is up-to-date. Do plugins impact whether you see an unRAID update? try running a ping from telnet to confirm you've got internet connectivity, other than that I suppose you could update manually by replacing bzimage & bzroot.
June 12, 201511 yr i just added this to extra parameters in a container that doesn't connect and it's connected after one reboot so far, not exactly rigorous testing i know... --dns 8.8.8.8 make that 2 reboots now. also sab and headphones are connecting with this in extra parameters.
June 12, 201511 yr i just added this to extra parameters in a container that doesn't connect and it's connected after one reboot so far, not exactly rigorous testing i know... --dns 8.8.8.8 Has worked for me too. Incidentally all my docker containers disappeared as well, docker.img is on a drive mounted with the plugin Unassigned Devices, this was mounted and docker.img was present. Restarted the docker service and all came up fine, so I assume that the docker service started before the drive was mounted.
June 12, 201511 yr Tom always asks if the host and the docker resolv.conf's match. Has anyone confirmed? Honestly, I'm not sure how to see the resolv.conf file for a docker...can someone enlighten me? John
June 12, 201511 yr Tom always asks if the host and the docker resolv.conf's match. Has anyone confirmed? Honestly, I'm not sure how to see the resolv.conf file for a docker...can someone enlighten me? John docker exec <container name> cat /etc/resolv.conf
June 12, 201511 yr i just added this to extra parameters in a container that doesn't connect and it's connected after one reboot so far, not exactly rigorous testing i know... --dns 8.8.8.8 make that 2 reboots now. also sab and headphones are connecting with this in extra parameters. 3 reboots and no connectivity issues with the containers i added it to.
June 12, 201511 yr i just added this to extra parameters in a container that doesn't connect and it's connected after one reboot so far, not exactly rigorous testing i know... --dns 8.8.8.8 make that 2 reboots now. also sab and headphones are connecting with this in extra parameters. 3 reboots and no connectivity issues with the containers i added it to. Trying now, will report back.
June 12, 201511 yr I'm still having trouble updating. I'm on rc4, but checking for plugin updates still says unRAID is up-to-date. Do plugins impact whether you see an unRAID update? try running a ping from telnet to confirm you've got internet connectivity, other than that I suppose you could update manually by replacing bzimage & bzroot. Thanks for the suggestion. I'm able to ping google from my unRAID box. Can you imagine some way user error could be at fault here? All I'm doing is hitting the Check for Updates button.
June 12, 201511 yr I'm still having trouble updating. I'm on rc4, but checking for plugin updates still says unRAID is up-to-date. Do plugins impact whether you see an unRAID update? try running a ping from telnet to confirm you've got internet connectivity, other than that I suppose you could update manually by replacing bzimage & bzroot. Thanks for the suggestion. I'm able to ping google from my unRAID box. Can you imagine some way user error could be at fault here? All I'm doing is hitting the Check for Updates button. Not even I can mess up clicking update... I think you've established it's not your fault.
June 12, 201511 yr I'm still having trouble updating. I'm on rc4, but checking for plugin updates still says unRAID is up-to-date. Do plugins impact whether you see an unRAID update? try running a ping from telnet to confirm you've got internet connectivity, other than that I suppose you could update manually by replacing bzimage & bzroot. Thanks for the suggestion. I'm able to ping google from my unRAID box. Can you imagine some way user error could be at fault here? All I'm doing is hitting the Check for Updates button. Maybe try checking your syslog for FAT-fs issues.
June 12, 201511 yr ....other than that my console is full of messages (see screenshot attached) but syslog is clean. Can you please give advise if this is an area of concern or how to deal with it? Rebooted my server - the console messages all disappeared...
June 12, 201511 yr i just added this to extra parameters in a container that doesn't connect and it's connected after one reboot so far, not exactly rigorous testing i know... --dns 8.8.8.8 make that 2 reboots now. also sab and headphones are connecting with this in extra parameters. 3 reboots and no connectivity issues with the containers i added it to. I set mine to --dns 192.168.1.1 and after a reboot they all connected. Worked.
June 12, 201511 yr i just added this to extra parameters in a container that doesn't connect and it's connected after one reboot so far, not exactly rigorous testing i know... --dns 8.8.8.8 make that 2 reboots now. also sab and headphones are connecting with this in extra parameters. 3 reboots and no connectivity issues with the containers i added it to. Does setting the overall dns for docker instead of on a container-basis achieve the same success? http://lime-technology.com/forum/index.php?topic=39604.msg376106.msg#376106
June 12, 201511 yr Does setting the overall dns for docker instead of on a container-basis achieve the same success? http://lime-technology.com/forum/index.php?topic=39604.msg376106.msg#376106 Ahh, so it was RC2 I started seeing this. Forgot all about your reply there Eric. I'll give it a go
Archived
This topic is now archived and is closed to further replies.