June 12, 201511 yr I am running a mediabuild version of bzimage/bzroot but I think I'm the only one here that is. wtf is that? You could always click the link in CHBMB's signature, it's pretty obvious due to the 8 lines and green links...
June 12, 201511 yr I have not tried rc6, yet, but just wanted to point out that ever since I reported a docker dns bug back in November/December of last year I have also been running with the --dns options in the main docker.cfg file as well as the file mapping of resolv.conf and have never run into the docker dns issues since that time. Yes that should do the trick. With the --dns option are you specifying an IP address that is not in the host /etc/resolv.conf file? What that option does is add that IP address as nameserver entries in the containers /etc/resolv.conf file. You can specify multiple --dns options as well. the --dns option only works for me if i use it in individual containers. if i put the same setting into the docker config file my containers fail to connect after a reboot.
June 12, 201511 yr I am running a mediabuild version of bzimage/bzroot but I think I'm the only one here that is. wtf is that? Media drivers added to bzroot for DVB support to use TVHeadEnd, it's been a thing since V5..
June 12, 201511 yr Author I am running a mediabuild version of bzimage/bzroot but I think I'm the only one here that is. wtf is that? Media drivers added to bzroot for DVB support to use TVHeadEnd, it's been a thing since V5.. Holy smokes I need to get out more
June 12, 201511 yr Author I have not tried rc6, yet, but just wanted to point out that ever since I reported a docker dns bug back in November/December of last year I have also been running with the --dns options in the main docker.cfg file as well as the file mapping of resolv.conf and have never run into the docker dns issues since that time. Yes that should do the trick. With the --dns option are you specifying an IP address that is not in the host /etc/resolv.conf file? What that option does is add that IP address as nameserver entries in the containers /etc/resolv.conf file. You can specify multiple --dns options as well. the --dns option only works for me if i use it in individual containers. if i put the same setting into the docker config file my containers fail to connect after a reboot. That makes no sense - not saying you're wrong, just that it doesn't agree with docker documentation on the subject: https://docs.docker.com/articles/networking/#dns
June 12, 201511 yr I have not tried rc6, yet, but just wanted to point out that ever since I reported a docker dns bug back in November/December of last year I have also been running with the --dns options in the main docker.cfg file as well as the file mapping of resolv.conf and have never run into the docker dns issues since that time. Yes that should do the trick. With the --dns option are you specifying an IP address that is not in the host /etc/resolv.conf file? What that option does is add that IP address as nameserver entries in the containers /etc/resolv.conf file. You can specify multiple --dns options as well. the --dns option only works for me if i use it in individual containers. if i put the same setting into the docker config file my containers fail to connect after a reboot. That makes no sense - not saying you're wrong, just that it doesn't agree with docker documentation on the subject: https://docs.docker.com/articles/networking/#dns I'm still perplexed by the screenshot Sparklyballs sent earlier of Sickbeard failing dns and command line docker exec working (which I'm able to reproduce). Next he's going to tell me Santa Claus doesn't exist... (Head explodes)
June 12, 201511 yr I have not tried rc6, yet, but just wanted to point out that ever since I reported a docker dns bug back in November/December of last year I have also been running with the --dns options in the main docker.cfg file as well as the file mapping of resolv.conf and have never run into the docker dns issues since that time. Yes that should do the trick. With the --dns option are you specifying an IP address that is not in the host /etc/resolv.conf file? What that option does is add that IP address as nameserver entries in the containers /etc/resolv.conf file. You can specify multiple --dns options as well. the --dns option only works for me if i use it in individual containers. if i put the same setting into the docker config file my containers fail to connect after a reboot. That makes no sense - not saying you're wrong, just that it doesn't agree with docker documentation on the subject: https://docs.docker.com/articles/networking/#dns I'm still perplexed by the screenshot Sparklyballs sent earlier of Sickbeard failing dns and command line docker exec working (which I'm able to reproduce). Next he's going to tell me Santa Claus doesn't exist... (Head explodes) tom needs to have a talk with you, lol..... (don't mention the easter bunny just yet)
June 12, 201511 yr I have not tried rc6, yet, but just wanted to point out that ever since I reported a docker dns bug back in November/December of last year I have also been running with the --dns options in the main docker.cfg file as well as the file mapping of resolv.conf and have never run into the docker dns issues since that time. Yes that should do the trick. With the --dns option are you specifying an IP address that is not in the host /etc/resolv.conf file? What that option does is add that IP address as nameserver entries in the containers /etc/resolv.conf file. You can specify multiple --dns options as well. I'm specifying the exact same ip address that I have setup in my dhcp server for dns server, which happens to be the network router [10.0.0.128], in the end its identical to hosts /etc/resolv.conf after dnsmasq/dhcp does its thing. I forgot I set the docker opts until it was brought up in here. Now I really should update my mappings to remove my RO mapping of resolv.conf.
June 12, 201511 yr So I am trying to prepare myself here... I had the DNS issue with numerous containers? I Edited/Saved each which resolved the issue. If I reboot my server will my containers have the DNS issue again or is that a perm fix? John
June 12, 201511 yr So I am trying to prepare myself here... I had the DNS issue with numerous containers? I Edited/Saved each which resolved the issue. If I reboot my server will my containers have the DNS issue again or is that a perm fix? John The issue crops up again for me, which is I think contradictory to what Tom stated earlier by re-pulling the containers from docker.
June 12, 201511 yr I have not upgraded yet because I am in the middle of a preclear. I have never experienced the DNS issue on earlier versions. Has this version caused that issue for anyone that didn't have it before?
June 12, 201511 yr I have not upgraded yet because I am in the middle of a preclear. I have never experienced the DNS issue on earlier versions. Has this version caused that issue for anyone that didn't have it before? For me it did.
June 12, 201511 yr Has this version caused that issue for anyone that didn't have it before? I have to edit/save my LMS docker in order for it to access wunderground. I never had to do that under rc5 or earlier.
June 12, 201511 yr Well after fighting with my system after updating to RC6 I started over fresh. I am having issues getting my shares working. I had in the past 3 shares named appdata,docker and images all located on my cache drive. I do not want the mover to move them so I had them set to cache only. I cannot seem to create them now since moving from RC4 to RC6. Any suggestions? Its been awhile since I setup shares so I could be doing wrong. Sorry if this is not the place to post this. Thanks JM
June 12, 201511 yr I was on RC5, updated my docker containers to remove my RO map to /etc/resolv.conf, upgraded to RC6 via the update wizard, rebooted the system, system started, dockers started, and dockers have network connectivity. So far, everything is working perfectly fine for me on RC6.
June 12, 201511 yr I have not upgraded yet because I am in the middle of a preclear. I have never experienced the DNS issue on earlier versions. Has this version caused that issue for anyone that didn't have it before? I had it once on RC2 but disappeared after a reboot. Never to reappear until RC6, although I've been following the threads on it. Was starting to think I was immune to it myself!
June 12, 201511 yr I was on RC5, updated my docker containers to remove my RO map to /etc/resolv.conf, upgraded to RC6 via the update wizard, rebooted the system, system started, dockers started, and dockers have network connectivity. So far, everything is working perfectly fine for me on RC6. I might delete my docker.img and start from a completely fresh install tomorrow when I get home. Beauty of having bought two licenses!
June 12, 201511 yr Well after fighting with my system after updating to RC6 I started over fresh. I am having issues getting my shares working. I had in the past 3 shares named appdata,docker and images all located on my cache drive. I do not want the mover to move them so I had them set to cache only. I cannot seem to create them now since moving from RC4 to RC6. Any suggestions? Its been awhile since I setup shares so I could be doing wrong. Sorry if this is not the place to post this. Thanks JM I usually set mine as hidden like .appdata
June 12, 201511 yr I have not upgraded yet because I am in the middle of a preclear. I have never experienced the DNS issue on earlier versions. Has this version caused that issue for anyone that didn't have it before? For me it did. Me too. Before RC6 I've not seen this issue, but it popped up in SickBeard today after upgrading. I checked the docker and it was in bridge mode, so I switched to host mode and all is good. I still have another couple of dockers that are in bridge mode, but they seem okay. I may switch them anyways. Honestly, I am not sure what the benefit of one over the other is anyways, but I likely just following the original recommendations for each docker as I built them.
June 13, 201511 yr Can you still export the share if it's set to hidden with .appdata? I spend a fair amount of time browsing to appdata on my Windows machine, that would be a deal breaker for me..
June 13, 201511 yr I am running a mediabuild version of bzimage/bzroot but I think I'm the only one here that is. wtf is that? You could always click the link in CHBMB's signature, it's pretty obvious due to the 8 lines and green links... Yeah, it's long, but pretty! Trying to help make PVR stuff a bit easier for folk..[emoji6]
June 13, 201511 yr Can you still export the share if it's set to hidden with .appdata? I spend a fair amount of time browsing to appdata on my Windows machine, that would be a deal breaker for me.. A hidden folder won't even appear on your shares page for you to configure it for export.
June 13, 201511 yr Can you still export the share if it's set to hidden with .appdata? I spend a fair amount of time browsing to appdata on my Windows machine, that would be a deal breaker for me.. A hidden folder won't even appear on your shares page for you to configure it for export. That's pretty much what I thought. Having said that, I could just go to my cache share and browse it from there.. I might well do that. Also will make it harder for the Mrs to access it and do untold damage...
June 13, 201511 yr Can you still export the share if it's set to hidden with .appdata? I spend a fair amount of time browsing to appdata on my Windows machine, that would be a deal breaker for me.. A hidden folder won't even appear on your shares page for you to configure it for export. That's pretty much what I thought. Having said that, I could just go to my cache share and browse it from there.. I might well do that. Also will make it harder for the Mrs to access it and do untold damage... I don't think you will be able to see it to browse it. You should be able to enter the path and see its contents though.
Archived
This topic is now archived and is closed to further replies.