On Wed, Jul 11, 2018 at 12:10 PM wrote:
> On Mon, Jul 09, 2018 at 05:00:49PM -0400, Jason Baron wrote:
> >
> >
> >On 07/08/2018 02:01 AM, Martin Kletzander wrote:
> >> On Thu, Jul 05, 2018 at 06:24:20PM +0200, Roman Mohr wrote:
> >>> On Thu, Jul 5, 2018 at 4:20 PM Jason Baron wrote:
> >>>
>
[Not sure who got this message, but it probably didn't get anywhere due to one
mailserver, so resending to make sure]
On Mon, Jul 09, 2018 at 05:00:49PM -0400, Jason Baron wrote:
On 07/08/2018 02:01 AM, Martin Kletzander wrote:
On Thu, Jul 05, 2018 at 06:24:20PM +0200, Roman Mohr wrote:
On
On 07/11/2018 06:10 AM, nert@wheatley wrote:
> On Mon, Jul 09, 2018 at 05:00:49PM -0400, Jason Baron wrote:
>>
>>
>> On 07/08/2018 02:01 AM, Martin Kletzander wrote:
>>> On Thu, Jul 05, 2018 at 06:24:20PM +0200, Roman Mohr wrote:
On Thu, Jul 5, 2018 at 4:20 PM Jason Baron wrote:
On Mon, Jul 09, 2018 at 05:00:49PM -0400, Jason Baron wrote:
>
>
> On 07/08/2018 02:01 AM, Martin Kletzander wrote:
> > On Thu, Jul 05, 2018 at 06:24:20PM +0200, Roman Mohr wrote:
> >> On Thu, Jul 5, 2018 at 4:20 PM Jason Baron wrote:
> >>
> >>> Hi,
> >>>
> >>> Opening tap devices, such as
On Mon, Jul 09, 2018 at 04:56:04PM -0400, Jason Baron wrote:
>
>
> On 07/05/2018 12:10 PM, Daniel P. Berrangé wrote:
> > On Thu, Jul 05, 2018 at 10:20:16AM -0400, Jason Baron wrote:
> >> Hi,
> >>
> >> Opening tap devices, such as macvtap, that are created in containers is
> >> problematic
On 07/08/2018 02:01 AM, Martin Kletzander wrote:
> On Thu, Jul 05, 2018 at 06:24:20PM +0200, Roman Mohr wrote:
>> On Thu, Jul 5, 2018 at 4:20 PM Jason Baron wrote:
>>
>>> Hi,
>>>
>>> Opening tap devices, such as macvtap, that are created in containers is
>>> problematic because the interface
On 07/05/2018 12:10 PM, Daniel P. Berrangé wrote:
> On Thu, Jul 05, 2018 at 10:20:16AM -0400, Jason Baron wrote:
>> Hi,
>>
>> Opening tap devices, such as macvtap, that are created in containers is
>> problematic because the interface for opening tap devices is via
>> /dev/tapNN and devtmpfs is
On Thu, Jul 05, 2018 at 06:24:20PM +0200, Roman Mohr wrote:
On Thu, Jul 5, 2018 at 4:20 PM Jason Baron wrote:
Hi,
Opening tap devices, such as macvtap, that are created in containers is
problematic because the interface for opening tap devices is via
/dev/tapNN and devtmpfs is not typically
On Thu, Jul 5, 2018 at 4:20 PM Jason Baron wrote:
> Hi,
>
> Opening tap devices, such as macvtap, that are created in containers is
> problematic because the interface for opening tap devices is via
> /dev/tapNN and devtmpfs is not typically mounted inside a container as
> its not namespace
On Thu, Jul 05, 2018 at 10:20:16AM -0400, Jason Baron wrote:
> Hi,
>
> Opening tap devices, such as macvtap, that are created in containers is
> problematic because the interface for opening tap devices is via
> /dev/tapNN and devtmpfs is not typically mounted inside a container as
> its not
Hi,
Opening tap devices, such as macvtap, that are created in containers is
problematic because the interface for opening tap devices is via
/dev/tapNN and devtmpfs is not typically mounted inside a container as
its not namespace aware. It is possible to do a mknod() in the
container, once the
11 matches
Mail list logo
