/1910/5
#working_hard_for_beer
Simos
>
> From: Ray Jender [mailto:rayjen...@gmail.com]
> Sent: Tuesday, May 22, 2018 11:25 AM
> To: lxc-users@lists.linuxcontainers.org
> Subject: [lxc-users] Networking Issues
>
>
>
> So, can anyone assist me in a LXD container network
s.
Thanks and I owe you a beer if I get this running with your help!
Thanks!
Ray
From: Ray Jender [mailto:rayjen...@gmail.com]
Sent: Tuesday, May 22, 2018 11:25 AM
To: lxc-users@lists.linuxcontainers.org
Subject: [lxc-users] Networking Issues
So, can anyone assist me in a LXD contain
So, can anyone assist me in a LXD container network issue?
How do you configure the networking so the containers have access to the
internet, as well as the internet having access to the container?
Right now I have one container on a Ubuntu 18.04 host. The Ubuntu host is
actually a Vbox VM wh
Hi all,
We are trying to convert our libvirt-lxc containers to LXC containers on CentOS
7 due to race conditions that are causing a lot of instability during our
testing of the former. I am currently testing against LXC 1.0.9 because it was
easily available to me in the EPEL repo, but I hope to
On 01/12/2016 07:03 PM, Fajar A. Nugraha wrote:
On Tue, Jan 12, 2016 at 9:29 PM, Peter Steele wrote:
On 01/12/2016 05:59 AM, Fajar A. Nugraha wrote:
On Tue, Jan 12, 2016 at 8:40 PM, Peter Steele wrote:
I should have added that I have no issue running our software on a single
EC2 instance wit
On Wed, Jan 13, 2016 at 10:03 AM, Fajar A. Nugraha wrote:
> On Tue, Jan 12, 2016 at 9:29 PM, Peter Steele wrote:
>> On 01/12/2016 05:59 AM, Fajar A. Nugraha wrote:
>>>
>>> On Tue, Jan 12, 2016 at 8:40 PM, Peter Steele wrote:
I should have added that I have no issue running our software
On Tue, Jan 12, 2016 at 9:29 PM, Peter Steele wrote:
> On 01/12/2016 05:59 AM, Fajar A. Nugraha wrote:
>>
>> On Tue, Jan 12, 2016 at 8:40 PM, Peter Steele wrote:
>>>
>>> I should have added that I have no issue running our software on a single
>>> EC2 instance with containers running on that inst
On 01/12/2016 05:59 AM, Fajar A. Nugraha wrote:
On Tue, Jan 12, 2016 at 8:40 PM, Peter Steele wrote:
I should have added that I have no issue running our software on a single
EC2 instance with containers running on that instance. We can assign
multiple IPs to the instance itself, as well as to
On Tue, Jan 12, 2016 at 8:40 PM, Peter Steele wrote:
> I should have added that I have no issue running our software on a single
> EC2 instance with containers running on that instance. We can assign
> multiple IPs to the instance itself, as well as to the containers running
> under the instance,
I should have added that I have no issue running our software on a
single EC2 instance with containers running on that instance. We can
assign multiple IPs to the instance itself, as well as to the containers
running under the instance, and the containers can all communicate with
each other as
On Tue, Jan 12, 2016 at 6:31 AM, Peter Steele wrote:
> From what I've read, I understand that Amazon has implemented some
> special/restricted behavior for the networking stack of EC2 instances. The
> question I have is whether I can accomplish what I've attempted here,
> specifically, can I acces
I first brought this issue up several weeks ago and have just got back
to the work where I originally ran into this problem. The scenario is
simple enough:
- Create two EC2 instances running CentOS 7.1
- Configure these instances to used bridged networking
- Create a LXC container running under
12 matches
Mail list logo
