On 03/18/2011 06:32 PM, Rob Landley wrote:
>> I guess the next step for me would be getting caching straight
>> as I will have the same mounts on several containers. What can I do to
>> help?
Oh, the _easy_ thing you can do for you use case is create the NFS mount
from the host and then --bind mou
On 03/18/2011 01:43 PM, Tim Spriggs wrote:
> On Fri, Mar 18, 2011 at 6:34 AM, Rob Landley wrote:
>> On 03/16/2011 01:51 PM, Tim Spriggs wrote:
>>> Thanks for the offer but I think I have networking under control. What
>>> is not working properly is that NFS happens from a host IP instead of
>>> a
On Fri, Mar 18, 2011 at 6:34 AM, Rob Landley wrote:
> On 03/16/2011 01:51 PM, Tim Spriggs wrote:
>> Thanks for the offer but I think I have networking under control. What
>> is not working properly is that NFS happens from a host IP instead of
>> a context IP... even though it is started from the
On 03/16/2011 01:51 PM, Tim Spriggs wrote:
> Thanks for the offer but I think I have networking under control. What
> is not working properly is that NFS happens from a host IP instead of
> a context IP... even though it is started from the context IP.
I'm working on that.
Here's the kernel patch
Thanks for the offer but I think I have networking under control. What
is not working properly is that NFS happens from a host IP instead of
a context IP... even though it is started from the context IP.
On Wed, Mar 16, 2011 at 1:55 AM, Jäkel, Guido wrote:
> Dear Tim,
>
> I guess you run into a p
Dear Tim,
I guess you run into a problem with the default routes -- if you don't apply
special things, there's only one default route! I struggled at start with the
same, it think. But I solved it. And I don't need an ip assigned to the bridges.
Please check at first, if CONFIG_IP_ADVANCED_ROU
