Public bug reported:
The presence of /var/lock/lxc-net causes service lxc-net start to
claim success but actually just do nothing useful.
When the system goes down hard, /var/lock/lxc-net is not removed, fair
enough. This means that systems require manual intervention after
booting.
You can
Good spot, thanks: /var/lock is on /, not a symlink to /var/run.
These machines are provisioned from OVH.com templates. I have raised a
support request with them to see if they are aware of this or are doing
anything strange on purpose.
--
$ cat /proc/self/mountinfo | fgrep lock
27 20 0:19 /
Public bug reported:
lxc is configured for limited user usage, i.e. the backing store is
always dir. Let's create a container, and snapshot it in its pristine
state:
% lxc-create -n restorebug -t download -- -d ubuntu -r utopic -a amd64
lxc-snapshot -n restorebug
[...]
lxc_container:
Public bug reported:
When starting a Vivid container, it fails to get an IP address. It
believes networking.service was successful, but actually it dies with
SIGPIPE. Restarting networking.service gets an IP, as expected.
Starting networking used to work with pre-vivid containers. I'm
This also occurs for limited user containers, without asking for a btrfs
backing store. This is more of a problem as the limited user can't
delete (or even detect) the subvolume themselves.
On a standard whole-partition-as-btrfs system, as setup by the installer, this
looks like:
ID 257 gen
No, that proposed work around seems to make no difference.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1452601
Title:
vivid container's networking.service fails on boot
Public bug reported:
Running lxc-stop on a container which doesn't exist actually creates the
container, and messes up its permissions, causing sequences like:
$ lxc-stop -n foo lxc-destroy -n foo lxc-clone clean-machine foo
..to fail with bad errors:
# it definitely doesn't exist to start
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
Yep, fixed.
With wily-proposed enabled,
# apt-get install lxc
installs:
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:amd64 1.1.5-0ubuntu0.15.10.2
2015-11-15 11:29:30 status installed lxc:amd64 1.1.5-0ubuntu0.15.10.2
Public bug reported:
Pulseaudio frequently crashes when Skype or some games (e.g. BigPharma from
Steam) are playing audio, it appears fine otherwise.
It gets restarted as my user (not as the system), and hence things can start
playing again, but neither Skype nor the games recover from this
Public bug reported:
Once systemd 226 is installed in an unprivileged Debian Sid container,
lxc-attach no-longer functions:
% lxc-attach -n siddy
lxc-attach: cgmanager.c: lxc_cgmanager_enter: 698 call to
cgmanager_move_pid_abs_sync failed: invalid request
lxc-attach: cgmanager.c: cgm_attach:
I switched to a build of Xenial's pulseaudio ages ago, and can confirm
it fixes this issue (although not the other).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
I have "reopened" this bug as:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718897 , as it
still fails for me (a month later).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
Public bug reported:
This specific release of libpulsecommon-11.1 is missing the symbol
`pa_encoding_from_string`.
This was fixed upstream: https://bugs.freedesktop.org/show_bug.cgi?id=103806
This has a Debian bug open, but I suspect it's been fixed by bumping major
version:
14 matches
Mail list logo
