Thank you!
Yes, you are right, eth0 says dhcp inside container - but where did that
come from? I have statically added the IP in the container config file..
Is there any way I can add the stuff you mentioned in
/etc/network/interfaces before starting the container, for e.g., in the
container confi
Quoting Vicky Kak (vicky@gmail.com):
> Hi All,
>
> I have been using linux container for some time as a user and now getting
> interested to know how it is internally working, I started looking for
> internals and could make that it is using cgroups under the hood.
> The docs mention that it i
You called __lxc_start() from where, how?
Quoting Vallevand, Mark K (mark.vallev...@unisys.com):
> I did this by calling __lxc_start(). So, lxc_check_inherited() didn't get
> called. That was this:
> > If I call __lxc_start() rather than lxc_start(), I see this:
> > vdr1: sync wake failure : Br
Thanks, yes, it is supposed to have dhcp via libvirt, and another VM's IP
in there:
br-int's current xml config has:
I added the foll. Line to br-int, but does not help:
?
Anjali
On 10/1/14 2:19 PM, "Stéphane Graber" wrote:
>On Wed, Oct 01, 2014 at 08:53:07PM +, A
Oh, I should have read your config a bit more closely :)
Anyway, your problem is probably that /etc/network/interfaces in the
container still says that eth0 is to be configured by dhcp.
You should either put your IP configuration in the container config or
in the container itself using the distro
Veth interface does get added to the br-int. It gets the IP 172.16.0.2
that it was given in the config file. On the container ifconfig eth0 shows:
ubuntu@vpfe:~$ ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:16:3e:4c:45:ae
inet addr:172.16.0.2 Bcast:172.255.255.255 Mask:255.0.
I did this by calling __lxc_start(). So, lxc_check_inherited() didn't get
called. That was this:
> If I call __lxc_start() rather than lxc_start(), I see this:
> vdr1: sync wake failure : Broken pipe
> vdr1: failed to spawn 'vdr1'
> And, just before that there is some complaining from valgrind:
If it takes along time to boot then it likely isn't
getting an ip address from dnmasq. Now last I checked
br-int does have a dnsmasq running, but double-check that.
You can lxc-attach to the container and manually do
sudo dhclient eth0
This is assuming that you are on a new enough lxc so that
th
On Wed, Oct 01, 2014 at 08:53:07PM +, Anjali Kulkarni wrote:
> Hi,
>
> I notice that If I add my beth link to any other bridge except lxcbr0, my
> ubuntu container takes a really long time to boot up, and seems to hang/wait
> for a long time after this statement:
> * Starting Bridge socket
Hi,
For the sake of testing I'd go ahead and just 'return 0' at the
top of lxc_check_inherited.
We can talk about adding an option to do this, i.e.
lxc.close_all_fds = -1 maybe. It's a very rare case where
that should be done, though.
-serge
Quoting Vallevand, Mark K (mark.vallev...@unisys.com
Hi,
I notice that If I add my beth link to any other bridge except lxcbr0, my
ubuntu container takes a really long time to boot up, and seems to hang/wait
for a long time after this statement:
* Starting Bridge socket events into upstart ...done.
My config file is:
…….
# Network configurati
On Wed, Oct 01, 2014 at 09:19:41PM +0100, Thouraya TH wrote:
> Hello,
> i have this on the first terminal:
> root@thouraya-Lenovo-3000-N500:~# lxc-attach -n u1
> root@u1:~# ls
> root@u1:~# ls
> root@u1:~#
>
> in the second, i have done:
> root@thouraya-Lenovo-3000-N500
> :/home/thouraya# sudo lxc-c
Hello,
i have this on the first terminal:
root@thouraya-Lenovo-3000-N500:~# lxc-attach -n u1
root@u1:~# ls
root@u1:~# ls
root@u1:~#
in the second, i have done:
root@thouraya-Lenovo-3000-N500
:/home/thouraya# sudo lxc-checkpoint -s -D /tmp/checkpoint -n u1
lxc_container: lxccontainer.c: exec_criu:
On Wed, 2014-10-01 at 15:05 +, Serge Hallyn wrote:
> Quoting Michael H. Warfield (m...@wittsend.com):
> > On Wed, 2014-10-01 at 13:53 +, Serge Hallyn wrote:
> > > Quoting Michael H. Warfield (m...@wittsend.com):
> > > > On Tue, 2014-09-30 at 19:39 -0400, Michael H. Warfield wrote:
> > > > >
Quoting Thouraya TH (thouray...@gmail.com):
> Hello,
>
> Please i need a help.
What distro/release are you on, and how did you install lxc?
> ##
> # The default user is 'ubuntu' with password 'ubuntu'!
> # Use the 'sudo' command to run tasks as root in the container.
> ##
>
> root@thouraya-Leno
Quoting Michael H. Warfield (m...@wittsend.com):
> On Wed, 2014-10-01 at 13:53 +, Serge Hallyn wrote:
> > Quoting Michael H. Warfield (m...@wittsend.com):
> > > On Tue, 2014-09-30 at 19:39 -0400, Michael H. Warfield wrote:
> > > > On Tue, 2014-09-30 at 23:56 +0100, Chris wrote:
> > > > > On 30/
On Wed, 2014-10-01 at 13:53 +, Serge Hallyn wrote:
> Quoting Michael H. Warfield (m...@wittsend.com):
> > On Tue, 2014-09-30 at 19:39 -0400, Michael H. Warfield wrote:
> > > On Tue, 2014-09-30 at 23:56 +0100, Chris wrote:
> > > > On 30/09/14 19:28, Michael H. Warfield wrote:
> > > > >> I haven'
Quoting Michael H. Warfield (m...@wittsend.com):
> On Tue, 2014-09-30 at 19:39 -0400, Michael H. Warfield wrote:
> > On Tue, 2014-09-30 at 23:56 +0100, Chris wrote:
> > > On 30/09/14 19:28, Michael H. Warfield wrote:
> > > >> I haven't looked a whole lot into the premade containers, my gut
> > > >
Hello,
Please i need a help.
##
# The default user is 'ubuntu' with password 'ubuntu'!
# Use the 'sudo' command to run tasks as root in the container.
##
root@thouraya-Lenovo-3000-N500:~# *sudo lxc-start -n u4*
lxc-start: lxc_start.c: main: 337 The container failed to start.
lxc-start: lxc_start
19 matches
Mail list logo
