On Thu, Jan 15, 2015 at 01:17:16PM -0500, Matt Micene wrote:
>
> Docker already supports a --dns option on the commandline to pass details
> for /etc/resolv.conf. For the various container solutions, I'd expect
> providing a standard consumable location for the resolver would be a good
> start.
You know what, I didn't realize you were planning on having the FAD on
Sunday. The one we're planning is on Thursday or Friday, which is the day
they generally give away space to projects for doing events like our FAD. I
apologize that I missed you planned on doing the FAD on Sunday. I'd love to
he
You know what, I didn't realize you were planning on having the FAD on
Sunday. The one we're planning is on Thursday or Friday, which is the day
they generally give away space to projects for doing events like our FAD. I
apologize that I missed you planned on doing the FAD on Sunday. I'd love to
he
Joe,
Not that we had formalized anything, but we already had plans to finish
https://github.com/vwbusguy/beefy-connection at the FAD at SCaLE 13x. I've
included Scott Williams (vwbusguy) so maybe it can be discussed there. Not
sure if I need to include the whole of the lists, but thought it wise t
Draft started here:
https://fedoraproject.org/wiki/FAD_SCALE_13x_Sunday_Cloud_and_Atomic
This is a call for help and participants. :-)
Best,
jzb
--
Joe Brockmeier | Principal Cloud & Storage Analyst
j...@redhat.com | http://community.redhat.com/
Twitter: @jzb | http://dissociatedpress.net/
On Thursday, 15 January 2015 11:47 PM, Matt Micene wrote:
>Docker already supports a --dns option on the commandline
>to pass details for /etc/resolv.conf.
I see.
>For the various container solutions, I'd expect providing
>a standard consumable location for the resolver would be a
>good start.
>
> Right, I've also heard about the special interface solution before.
> Not sure how exactly it works though.
Can't claim to be an expert on the implementation details either, sorry.
I see. In that case, maybe we could have local resolver listening
> on multiple network interfaces. But how wo
Hello Matt,
On Thursday, 15 January 2015 8:27 PM, Matt Micene wrote:
>One of the on list responses talks about setting up a known
>IP space, taking a page from MS and using a local collision domain.
>AWS does this currently, making a metadata service available from
>all instances on 169.254.169
Hello Daniel,
Thank you so much for the detailed response, much appreciate it.
> On Thursday, 15 January 2015 7:47 PM, Daniel P. Berrange wrote:
> NB this won't just be a Docker problem. It has the potential to affect any
> container technology. eg a simple libvirt LXC container can be setup s
On Thu, Jan 15, 2015 at 10:09:23AM -0500, Colin Walters wrote:
>
>
> On Thu, Jan 15, 2015, at 08:57 AM, P J P wrote:
>
> > I'm no expert on Docker(or container) applications. I was wondering if
> > someone
> > could help in testing Docker(or container) applications with the local
> > DNSSEC
>
On Thu, Jan 15, 2015, at 08:57 AM, P J P wrote:
> I'm no expert on Docker(or container) applications. I was wondering if someone
> could help in testing Docker(or container) applications with the local DNSSEC
> validating resolver on F21.
See https://github.com/docker/docker/pull/9239
My thoug
This gets worse when you add an overlay network provider, like flannel in
Atomic, which provides a tunneled or encapsulated network to Docker
containers that isn't accessible from the host.
One of the on list responses talks about setting up a known IP space,
taking a page from MS and using a loca
On Thu, Jan 15, 2015 at 01:57:59PM +, P J P wrote:
>Hello all,
>
> Please see:
> -> https://fedoraproject.org/wiki/Changes/Default_Local_DNS_Resolver
> -> https://pjps.wordpress.com/2014/05/02/local-dns-resolver-in-fedora/
>
>
> This is an upcoming F22 feature; it proposes to install
Hello all,
Please see:
-> https://fedoraproject.org/wiki/Changes/Default_Local_DNS_Resolver
-> https://pjps.wordpress.com/2014/05/02/local-dns-resolver-in-fedora/
This is an upcoming F22 feature; it proposes to install a local DNSSEC
validating DNS resolver running at 127.0.0.1:53 on Fed
14 matches
Mail list logo