On Wednesday 08 February 2012 03:54 AM, Serge Hallyn wrote:
@Ritesh,
Unfortunately I don't know that that many people would read the README :)
It is worth adding though, thanks for the suggestion.
In addition, I will add an LXC section to the ubuntu server guide soon,
and this should be
On 08/02/12 08:33, Ritesh Raj Sarraf wrote:
On Wednesday 08 February 2012 03:54 AM, Serge Hallyn wrote:
@Ritesh,
Unfortunately I don't know that that many people would read the README :)
It is worth adding though, thanks for the suggestion.
In addition, I will add an LXC section to the
Thanks Ritesh and Simon, sounds like a great idea.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/925511
Title:
lxc init script should fail when it ... failed
To manage notifications
On Wednesday 08 February 2012 03:54 AM, Serge Hallyn wrote:
@Ritesh,
Unfortunately I don't know that that many people would read the README :)
It is worth adding though, thanks for the suggestion.
In addition, I will add an LXC section to the ubuntu server guide soon,
and this should be
On 08/02/12 08:33, Ritesh Raj Sarraf wrote:
On Wednesday 08 February 2012 03:54 AM, Serge Hallyn wrote:
@Ritesh,
Unfortunately I don't know that that many people would read the README :)
It is worth adding though, thanks for the suggestion.
In addition, I will add an LXC section to the
Thanks Ritesh and Simon, sounds like a great idea.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/925511
Title:
lxc init script should fail when it ... failed
To manage notifications about this bug
@Ritesh,
the dnsmasq for the lxc bridge explicitly binds only lxcbr0. So if that
fails, then your other dnsmasq has already bound all interfaces.
If /etc/init.d/lxc fails to start now, then lxcbr0 never had dhcp
before. If you're not using lxcbr0 for your containers, then you can
simply set
On Tuesday 07 February 2012 09:19 PM, Serge Hallyn wrote:
@Ritesh,
the dnsmasq for the lxc bridge explicitly binds only lxcbr0. So if that
fails, then your other dnsmasq has already bound all interfaces.
Yes. Because I had dnsmasq installed by default. From the dnsmasq.conf
file's
@Ritesh,
Unfortunately I don't know that that many people would read the README :)
It is worth adding though, thanks for the suggestion.
In addition, I will add an LXC section to the ubuntu server guide soon,
and this should be mentioned there.
I'm also marking this (and the equivalent libvirt)
Actually - to affect dnsmasq this should be a new bug. Opened bug
928524 to track it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/925511
Title:
lxc init script should fail when it
@Ritesh,
the dnsmasq for the lxc bridge explicitly binds only lxcbr0. So if that
fails, then your other dnsmasq has already bound all interfaces.
If /etc/init.d/lxc fails to start now, then lxcbr0 never had dhcp
before. If you're not using lxcbr0 for your containers, then you can
simply set
On Tuesday 07 February 2012 09:19 PM, Serge Hallyn wrote:
@Ritesh,
the dnsmasq for the lxc bridge explicitly binds only lxcbr0. So if that
fails, then your other dnsmasq has already bound all interfaces.
Yes. Because I had dnsmasq installed by default. From the dnsmasq.conf
file's
@Ritesh,
Unfortunately I don't know that that many people would read the README :)
It is worth adding though, thanks for the suggestion.
In addition, I will add an LXC section to the ubuntu server guide soon,
and this should be mentioned there.
I'm also marking this (and the equivalent libvirt)
Actually - to affect dnsmasq this should be a new bug. Opened bug
928524 to track it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/925511
Title:
lxc init script should fail when it ... failed
To
So how is it supposed to behave now?
I just did the upgrade and:
Setting up lxc (0.7.5-3ubuntu18) ...
Installing new version of config file /etc/init.d/lxc ...
* Starting Linux Containers
dnsmasq:
So how is it supposed to behave now?
I just did the upgrade and:
Setting up lxc (0.7.5-3ubuntu18) ...
Installing new version of config file /etc/init.d/lxc ...
* Starting Linux Containers
dnsmasq:
** Branch linked: lp:~serge-hallyn/ubuntu/precise/lxc/lxc-start-
checkperms
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/925511
Title:
lxc init script should fail when it ... failed
This bug was fixed in the package lxc - 0.7.5-3ubuntu17
---
lxc (0.7.5-3ubuntu17) precise; urgency=low
[ Serge Hallyn ]
* 0032-start-check-caps.patch: exit early and with a clear error message
if lxc-start is run with insufficient permissions. (LP: #925520)
*
** Branch linked: lp:~serge-hallyn/ubuntu/precise/lxc/lxc-start-
checkperms
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/925511
Title:
lxc init script should fail when it ... failed
To manage
This bug was fixed in the package lxc - 0.7.5-3ubuntu17
---
lxc (0.7.5-3ubuntu17) precise; urgency=low
[ Serge Hallyn ]
* 0032-start-check-caps.patch: exit early and with a clear error message
if lxc-start is run with insufficient permissions. (LP: #925520)
*
20 matches
Mail list logo
