[lxc-devel] Networking

2020-04-07 Thread Saint Michael
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

[lxc-devel] Network Manager makes RHEL 8 and Centos 8 impossible to use as a container

2019-12-19 Thread Saint Michael
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 because

[lxc-devel] Incrond service fails inside a container

2018-05-11 Thread Saint Michael
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 n

[lxc-devel] lxc.autodec and fuse

2017-11-17 Thread Saint Michael
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

[lxc-devel] LXC networking bug

2016-11-25 Thread Saint Michael
In LXC networking type phys, the network interface correctly disappears from the host, but the container never "returns" the device when it gets stopped, and it never starts again, unless the host is rebooted, since the device is not there. I think the device should go back to the host so the conta

[lxc-devel] Networking issue

2016-11-25 Thread Saint Michael
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

[lxc-devel] Fuse fails inside container from last week

2016-07-28 Thread Saint Michael
When I try to use fuse in a container, I get fuse: failed to open /dev/fuse: Operation not permitted In my config file I have lxc.mount.entry = /dev/fuse dev/fuse none bind,create=file How can I get back to be able to use fuse inside a container? rpm -qa | grep -i lxc lxc-libs-2.0.3-1.el7.centos

[lxc-devel] FUSE stopped working inside containers

2016-07-28 Thread Saint Michael
​​rpm -qa | grep lxc lxc-libs-1.1.5-1.fc22.x86_64 lxc-1.1.5-1.fc22.x86_64 Since the latest changes in ​LXC, I am out of business, since Fuse does not work anymore inside containers, and that is what I use for a line-of-production application that maps an FTP server to /mnt ​ ​fuse is loaded, which