As you probably know, the only way to have a Vmware VM with containers is
to enable promiscuous mode, that that kills the network performance and
causes high CPU usage for every other VM. So far the only way to
containerize under Vsphere is to add the max 10 interfaces allowed by
Vmware and assign
Network Manager makes RHEL 8 and Centos 8 impossible to conteinarize.
Please see that it detects a device type macvlan, when it should be really
Ethernet. nmcli connection up Ethernet0 Error: Connection activation
failed: No suitable device found for this connection (device lo not
available
I cannot get the service incrond to work inside a container.
This service uses inotify to monitor the FS for changes.
My systctl.conf has plenty of watches, etc. That is not the issue
These are privileged containers.
Does anybody have any idea why this service does work on the host just fine
and
I detected a big problem. If I set lxc.autodev=1 then I cannot load the
fuse driver inside a container, and my app fails to work. I mount an ftp
server to /mnt. But if I use lxc.autodev=0, fuse works but then the
container hijacks the TTY of the host on bootinh, to the poing where in
order to even
It was working fine until a week ago.
I have two sites, it happened on both, so the issue is not on my router or
my switch, since they are different sites and we did not upgrade anything.
Ubuntu 16.04.1 LTS (GNU/Linux 4.4.0-45-generic x86_64)
LXC installed from apt-get install lxc1
iptables off in