similar to: Host loses network connectivity when starting containers

I've created an EC2 AMI for AWS that essentially represents a CentOS 7 "hypervisor" image. I deploy instances of these in AWS and create an number of libvirt based lxc containers on each of these instances. The containers run fine within a single host and have no problem communicating with themselves as well as with their host, and vice versa. However, containers hosted in one

On 04/01/2016 02:07 PM, Laine Stump wrote: > On 03/31/2016 06:43 PM, Peter Steele wrote: >> I've created an EC2 AMI for AWS that essentially represents a CentOS >> 7 "hypervisor" image. I deploy instances of these in AWS and create >> an number of libvirt based lxc containers on each of these instances. >> The containers run fine within a single host and

In the "other" LXC project (linuxcontainers.org), you can map a host's physical ethernet interface to a container, e.g. lxc.network.type = phys lxc.network.flags = up lxc.network.link = eth1 lxc.network.name = eth1 Is there an equivalent option for doing this with libvirt lxc? Peter

Hi, I noticed that libvirt-lxc will be deprecated for RedHat: "Future development on the Linux containers framework is now based on the docker command-line interface. libvirt-lxc tooling may be removed in a future release of Red Hat Enterprise Linux (including Red Hat Enterprise Linux 7) and should not be relied upon for developing custom container management applications." -

On 04/11/2016 11:33 AM, Laine Stump wrote: > Interesting. That functionality was moved out of the kernel's bridge > module into br_netfilter some time back, but that was done later than > the kernel 3.10 that is used by CentOS 7. Are you running some later > kernel version? > > If your kernel doesn't have a message in dmesg that looks like this: > > bridge:

On 04/02/2016 05:20 PM, Laine Stump wrote: > You say they can talk among containers on the same host, and with their > own host (I guess you mean the virtual machine that is hosting the > containers), but not to containers on another host. Can the containers > communicate outside of the host at all? If not, perhaps the problem is > iptables rules for the bridge device the containers

Dear all, I wonder if libvirt can work on Ubuntu. As you know, it is very convenient to install libvirt on Fedora. I can download the libvirt packet from libvirt.org and install it using command ./configure, make and make install. As I am going to install an open source simulation system named openairinterface, Ubuntu is the recommended OS, and I want to install the simulation system in libvirt

Hello Is there a way to set custom environment variables for LXC containers so that it is available for all processes within the container? The libvirt-lxc driver seems to be setting up only the below variables (as per the docs), but there doesn't seem to be a way customize it. containerThe fixed string libvirt-lxc to identify libvirt as the creator container_uuidThe UUID assigned to the

On June 1, 2020 00:32:23 Roy Eastwood via samba <samba at lists.samba.org> wrote: > Sorry, send to list as well >> I've set up Samba 4.11 in an unprivileged container. At this point, I can >> only assume that this might be the issue here, though I > can't >> quite understand why. Does anyone happen to have an explanation, is there >> maybe a

On 04/01/2016 07:04 PM, Peter Steele wrote: > On 04/01/2016 02:07 PM, Laine Stump wrote: >> On 03/31/2016 06:43 PM, Peter Steele wrote: >>> I've created an EC2 AMI for AWS that essentially represents a CentOS >>> 7 "hypervisor" image. I deploy instances of these in AWS and create >>> an number of libvirt based lxc containers on each of these

On 03/31/2016 06:43 PM, Peter Steele wrote: > I've created an EC2 AMI for AWS that essentially represents a CentOS 7 > "hypervisor" image. I deploy instances of these in AWS and create an > number of libvirt based lxc containers on each of these instances. The > containers run fine within a single host and have no problem > communicating with themselves as well as

On 04/12/2016 01:37 PM, Peter Steele wrote: > On 04/11/2016 11:33 AM, Laine Stump wrote: I wouldn't be too quick to > judgement. First take a look at tcpdump on the bridge interface that > the containers are attached to, and on the ethernet device that > connects the bridge to the rest of Amazon's infrastructure. If you see > packets from the container's IP going out

Mandi! Andrew Bartlett via samba In chel di` si favelave... > There is a limitation for containers regarding xattrs as I understand > it, so you may need to go to a full DC. ...googling around seems to me that are ''old limitation'', now gone. I've also hitted: https://lists.linuxcontainers.org/pipermail/lxc-devel/2015-November/012789.html so seems that

On 04/07/2016 09:50 AM, Peter Steele wrote: > On 04/02/2016 05:20 PM, Laine Stump wrote: >> You say they can talk among containers on the same host, and with their >> own host (I guess you mean the virtual machine that is hosting the >> containers), but not to containers on another host. Can the containers >> communicate outside of the host at all? If not, perhaps the

On 2/6/2017 2:05 ??, hw wrote: > That?s a good thing, though it can be difficult to run systems > using ancient software. You may want to check the following paradigm (from another open source perl-based application) to create a Perl environment within your system, avoiding to tamper with it: https://metacpan.org/pod/App::Netdisco#Installation We are running it in production for

I'm starting to deploy my new domain in my organization, setting up the new domain and DCs. I'm following the recommendation to create the DCs as ''DC only'', eg with only samba and a root access for ssh. Having to choose between VMs and Containers (LXC), there's differences between them that can involve samba features/performances? Filesystem limitation? Seems to

On Tue, Aug 11, 2015 at 08:31:02AM +0200, Martin Kletzander wrote: > On Mon, Aug 10, 2015 at 09:50:04PM +0100, Mark Clarkson wrote: > >Hi, > >I noticed that libvirt-lxc will be deprecated for RedHat: > > > >"Future development on the Linux containers framework is now based on > >the docker command-line interface. libvirt-lxc tooling may be removed > >in

Dear all, I am slowly building a Arch Linux VM guest on my Arch Linux host. The guest machine is now built and is recognized as shown by this command : gabx@hortensia ➤➤ ~ % machinectl list MACHINE CONTAINER SERVICE dahlia container nspawn 1 machines listed. I an following the libvirt.org documentation. Now, according this page[1] about lxc

How can I run command in containers on the host? Just like the lxc command lxc-attach. I run : virsh -c lxc:/// lxc-enter-namespace fedora2 --noseclabel /bin/ls but get error: libvirt: error : Expected at least one file descriptor error: internal error: Child process (14930) unexpected exit status 125 Here is my libvirt.xml <domain type='lxc'> <name>fedora2</name>

Hi, Is there a way to backup KVM Guest VM running CentOS Linux release 7.9.2009 (Core) OS in kvmguestosimage.ova or kvmguestosimage.vmdk format as I am trying to restore it in AWS by referring to https://aws.amazon.com/ec2/vm-import/ article as per the below supported file format. [1] Open Virtualization Archive (OVA) [2] Virtual Machine Disk (VMDK) [3] Virtual Hard Disk (VHD/VHDX) [4] raw Also