I haven't seen this issue for ages, using primarily sid and wily guests.
Trying again on my desktop, which definitely used to have the issue, I
can't reproduce it, using:
2015-11-15 11:29:28 status installed liblxc1:amd64 1.1.5-0ubuntu0.15.10.2
2015-11-15 11:29:29 status installed python3-lxc:amd
What I should do is try to back out some of my changes and determine
whether I can duplicate the problem.
Then I can determine which changes matter and which ones don't.
I won't have time for a few days, but I will do my best.
--
You received this bug notification because you are a member of Ub
How about a comment in the /etc/default/lxc-net file?
I guess the question is - when it broke for you, which files did you
first look at to try to fix it?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.laun
I suggest that README.Debian (or Ubuntu) mention the workarounds
regarding bind9 and ipv6.
It might save some time in debugging lxc problems.
--
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/bug
@faux
do you still have this issue?
--
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/1452601
Title:
vivid container's networking.service fails on boot with signal=PIPE
To manage notific
And suddenly, it has started working.
I don't know why.
I did a reboot
sudo systemctl status lxc-net
The above command suddenly had results which looked familiar, in a good way.
Before this, I had unsuccessfully tried a few of the sample lxc.
Perhaps I updated something which fixed the proble
What does
sudo /usr/lib/x86_64-linux-gnu/lxc/lxc-net stop
sudo /usr/lib/x86_64-linux-gnu/lxc/lxc-net start
sudo netstat -lap| grep LISTEN
show now that you've updated bind9's configuration?
** This bug is no longer a duplicate of bug 1240757
Bridge not created if bind
*** This bug is a duplicate of bug 1240757 ***
https://bugs.launchpad.net/bugs/1240757
I had missed restart lxc-net.
Unfortunately, that didn't make any difference.
kevin@awabi:~$ sudo lxc-start -n escale_build --logfile /tmp/lxc-log
--logpriority 3 -F
lxc-start: conf.c: instantiate_veth: 2
*** This bug is a duplicate of bug 1240757 ***
https://bugs.launchpad.net/bugs/1240757
Quoting Kevin Dalley (1452...@bugs.launchpad.net):
> *** This bug is a duplicate of bug 1240757 ***
> https://bugs.launchpad.net/bugs/1240757
>
> I have now added
>
> listen-on-v6 { none; };
> re
*** This bug is a duplicate of bug 1240757 ***
https://bugs.launchpad.net/bugs/1240757
I have now added
listen-on-v6 { none; };
restarted bind9, and again nothing:
kevin@awabi:~/src$ sudo lxc-start -n escale_build --logfile /tmp/lxc-log
--logpriority 3 -Flxc-start: conf.c: instantia
*** This bug is a duplicate of bug 1240757 ***
https://bugs.launchpad.net/bugs/1240757
Thanks for your help.
Unfortunately, I didn't have any luck with this either.
I added
listen-on { ! 10.0.3.1; };
just before the final "}" line.
restarted bind9, and I have the same error messag
*** This bug is a duplicate of bug 1240757 ***
https://bugs.launchpad.net/bugs/1240757
D'oh! thanks for that info. You are running bind9, which is causing
the conflict. To work around this, you can tell bind9 to not listen
on 10.0.3.1 - see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug
kevin@awabi:~/notes/security$ sudo netstat -lap| grep LISTEN
[sudo] password for kevin:
tcp0 0 usscc-mvetter.co:domain *:* LISTEN
1192/named
tcp0 0 192.168.43.174:domain *:* LISTEN
1192/named
tcp0
You're still getting
dnsmasq: failed to create listening socket for 10.0.3.1: Cannot
assign requested address
What does
sudo netstat -lap| grep LISTEN
show?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubun
Thanks again.
kevin@awabi:~/tmp$ sudo /usr/lib/x86_64-linux-gnu/lxc/lxc-net stop
kevin@awabi:~/tmp$ sudo /usr/lib/x86_64-linux-gnu/lxc/lxc-net start
dnsmasq: failed to create listening socket for 10.0.3.1: Cannot assign
requested address
Failed to setup lxc-net.
kevin@awabi:~/tmp$ sudo brctl sho
Ok, so the error msg is simply misleading - it says 'permission denied',
but the bridge does not exist.
Can you please show:
sudo /usr/lib/x86_64-linux-gnu/lxc/lxc-net stop
sudo /usr/lib/x86_64-linux-gnu/lxc/lxc-net start
sudo brctl show
and see if your container now starts?
Please also paste /
Thanks.
kevin@awabi:~$ sudo brctl show
bridge name bridge id STP enabled interfaces
virbr0 8000.52540063031d yes virbr0-nic
kevin@awabi:~$ sudo ifconfig -a
loLink encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
Thanks, what about
sudo brctl show
sudo ifconfig -a
sudo journalctl -u lxc-net
sudo systemd-detect-virt
--
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/1452601
Title:
vivid container's
Thanks.
kevin@awabi:~$ sudo lxc-start -n escale_build -F -l trace -o /dev/stdout
lxc-start 1446650865.960 INFO lxc_start_ui - lxc_start.c:main:264 -
using rcfile /var/lib/lxc/escale_build/config
lxc-start 1446650865.961 WARN lxc_confile -
confile.c:config_pivotdir:1801 - lxc.
Hi,
you're actually geting EPERM, which means lxcbr0 exists. Please show
the output of:
sudo lxc-start -n escale_build -F -l trace -o /dev/stdout
sudo brctl show
sudo ifconfig -a
sudo journalctl -u lxc-net
sudo systemd-detect-virt
--
You received this bug notification because you are a member
Host is:
Linux awabi 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
container is:
Linux escalebuild 3.16.0-51-generic #69~14.04.1-Ubuntu SMP Wed Oct 7
15:32:41 UTC 2015 x86_64 GNU/Linux
here is output from my attempt to start:
kevin@awabi:~$ sudo lx
@Kevin,
could you please give some more details? In particular, release of both
host and container, where exactly it fails, and the relevant journalctl
output.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bug
I upgraded to Wiley, and the problem has shown up again. I haven't
managed to fix it yet under Wiley, though I could fix it under Vivid
--
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/14526
I just created a vivid container on a vivid host, and got:
root@v1:~# systemctl status networking.service
● networking.service - LSB: Raise network interfaces.
Loaded: loaded (/etc/init.d/networking)
Drop-In: /run/systemd/generator/networking.service.d
└─50-insserv.conf-$network.co
Just setting up a fresh Vivid LXC host machine + I was incorrect above.
There's no requirement for /etc/dnsmasq.conf to exist for lxc-net to
start correctly.
There is a requirement though for /etc/resolv.conf to reference at least
one valid name server.
--
You received this bug notification bec
I had to remove both lines, in my case.
And this is likely a less than correct fix. I'm under the gun to get a
client machine I'm hosting setup to run many of their sites in LXC
containers, so time I invested looking at this fix was minimal.
Likely the entire stop function is best revisited, to a
1. Do you need to remove both lines, or is only removing the second line
sufficient?
2. Does anyone still get this on wily? My wily laptop and vms have no
problem.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https:/
Removing the 2 lines suggested by davidfavor, actually fixed my problem
- after restarting lxc-net
(/etc/dnsmasq.conf was never empty for me)
--
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/bug
Oh, I see...
I was using OOM as an example. I this case, it appears the missing
/etc/dnsmasq.conf file might be the culprit.
So first start of lxc-net, dnsmasq never starts.
After that, it will never start, unless a hard reboot is done.
--
You received this bug notification because you are a m
Oh... and - touch /etc/dnsmasq.conf - is still required, so this is
another bug to be fixed.
--
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/1452601
Title:
vivid container's networking.s
Okay, a simple fix that seems to work (at least in my case), is to
comment out the first two guards in the stop function.
So...
#[ "x$USE_LXC_BRIDGE" = "xtrue" ] || { exit 0; }
#[ -f "${varrun}/network_up" ] || { exit 0; }
Once these are skipped, the code seems to work.
--
You received this bu
IMHO, systemd seems to be the root of all evil.
touch /etc/dnsmasq.conf has no effect.
net4-dev# systemctl restart lxc-net
net4-dev# systemctl status lxc-net
● lxc-net.service - LXC network bridge setup
Loaded: loaded (/lib/systemd/system/lxc-net.service; enabled; vendor preset:
enabled)
A
For me, it was a matter of creating an empty /etc/dnsmasq.conf so that
lxc-net.service could start, thus creating lxcbr0
--
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/1452601
Title:
vi
This bug affects gitian-builder when used with lxc. Gitian-builder is
the reproducible build tools used by Bitcoin Core and other projects.
The relevant gitian-builder bug is https://github.com/devrandom/gitian-
builder/issues/95.
I have confirmed this bug with a 15.04 chroot. As you can see from
No, that proposed work around seems to make no difference.
--
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/1452601
Title:
vivid container's networking.service fails on boot with signal=P
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
--
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/1452601
Title:
vivid container's networking.service fails on boot with signal
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
--
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/1452601
T
Does the workaround mentioned in
https://lists.linuxcontainers.org/pipermail/lxc-
users/2015-May/009098.html work for you?
--
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/1452601
Title:
38 matches
Mail list logo
