>
> The only thing that still works is phys, at least in Vmware virtual
> machines and the new kernel 5.0X
Any idea how can we make macvlan work again?
> Philip
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
On Fri, Feb 28, 2020 at 08:12:17PM +0100, Christian Brauner wrote:
> On February 28, 2020 8:09:45 PM GMT+01:00, "Serge E. Hallyn"
> wrote:
> >On Fri, Feb 28, 2020 at 02:34:25PM +0100, Ede Wolf wrote:
> >> Hello,
> >>
> >> do we have any alternatives to classical bridging right now for
>
On February 28, 2020 8:09:45 PM GMT+01:00, "Serge E. Hallyn"
wrote:
>On Fri, Feb 28, 2020 at 02:34:25PM +0100, Ede Wolf wrote:
>> Hello,
>>
>> do we have any alternatives to classical bridging right now for
>connecting
>> (to) unprivileged containers? Like macvlan or ipvlan?
>>
>> If so, I may
On Fri, Feb 28, 2020 at 02:34:25PM +0100, Ede Wolf wrote:
> Hello,
>
> do we have any alternatives to classical bridging right now for connecting
> (to) unprivileged containers? Like macvlan or ipvlan?
>
> If so, I may haved missed the documentation, otherwise, are there any plans
> to
On 2/28/20 5:34 AM, Ede Wolf wrote:
Hello,
do we have any alternatives to classical bridging right now for
connecting (to) unprivileged containers? Like macvlan or ipvlan?
If so, I may haved missed the documentation, otherwise, are there any
plans to incorporate those options? Or maybe
Dear Harri,
I don't check it yet, but is -XX:+UseContainerSupport a requirement for this??
>root@c526096eb86e:/# java -XX:MaxRAMPercentage=20.0 -XX:MinRAMPercentage=10.0
>-XX:+PrintFlagsFinal -
>root@debian10:~# java -XX:MaxRAMPercentage=20.0 -XX:MinRAMPercentage=10.0
>-XX:+PrintFlagsFinal
Hello,
do we have any alternatives to classical bridging right now for
connecting (to) unprivileged containers? Like macvlan or ipvlan?
If so, I may haved missed the documentation, otherwise, are there any
plans to incorporate those options? Or maybe there are sound reasons not
do at all?
Hi folks,
according to some notes on the net (e.g. [1]) openjdk11 is aware of
the container limits for calculating default heap size and some
other internal parameters. Apparently this works very well for
Docker. Sample:
# docker run -ti --rm --cpus 2 -m 4G debian
root@c526096eb86e:/# apt
