@Jens
this is very dependent on your exact setup, so please open a new
bug specifying your precise host environment (release, any ppas,
package versions, any custom configuration, and error logs if possible)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Today I upgraded our last utopic containers (~10) to vivid using do-
release-upgrade: Everywhere the same: after reboot systemd is the only
thing which is running in the container, but nothing else happens. It
doesn't start anything! So the only way to get the stuff fixed is to
manually attach to t
The problem is fixed but needs additional comment.
I've had a problem after upgrading only lxc package from trusty-backports.
The network was not working in debian jessie and after logging in (lxc-attach)
systemd was not working correctly.
The solution was to update not only lxc package but also l
Fixed through trusty-backports.
** Changed in: lxc (Ubuntu Trusty)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1347020
Title:
systemd does not boot in a con
I'm usingTrusty (14.04.2) trying to run debian/jessie in lxc
what i did:
$ add-apt-repository ppa:ubuntu-lxc/daily
$ apt-get update
$ apt-get install lxc cgmanager lxcfs
then:
$ lxc-create -n jessie -t debian
$ lxc-start -n jessie
nothing seems to happen
in the syslog i see:
Jul 31 20:07:05 ubu
I'm running utopic with latest updates. Any container, which has systemd
running simply hangs, when /sbin/init gets started (no matter, whether
config has 'lxc.kmsg = 0' or not). Tried it previously with a trusty and
today with a vivid container. So wondering, whether there is a bugfix
available a
Thank you Stephane for your PPA! I installed 14.04 expecting LXC to just
work, found that it didn't, somehow found this page, installed your PPA
and the updated utilities and it now appears to be working perfectly! I
only wish it would work out of the box in an LTS release.
--
You received this b
Not anytime soon unfortunately. The backport of all the needed bits as
SRUs will be very very tricky to get right, currently our timeframe is
"by 16.04".
If you're maintaining a PPA already, you could pick up the required
trusty packages from ppa:ubuntu-lxc/daily or just include your own
backports
Any ideas when this will be fixed in Trusty? This is blocking
unity8-lxc from working anymore on Trusty hosts.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1347020
Title:
systemd does not boot in
With latest lxc and lxcfs this works now, both system and session
containers with systemd, with systemd on the host.
** Changed in: lxc (Ubuntu)
Status: Triaged => Fix Released
** Changed in: lxc (Ubuntu Trusty)
Assignee: (unassigned) => Stéphane Graber (stgraber)
--
You received th
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) => Stéphane Graber (stgraber)
** Changed in: lxc (Ubuntu)
Milestone: None => ubuntu-15.01
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1347
I prepared a minimal vivid container with systemd-sysv, and tried to
boot it (vivid host):
$ sudo lxc-start -n vivid-systemd -F
Failed to mount cgroup at /sys/fs/cgroup/systemd: Permission denied
[... hangs ...]
In apparmor I see:
[10072.122514] audit: type=1400 audit(1416213339.298:50): apparmor
Retitling the bug to be more general, and adding a trusty task to
reflect the original "trusty host" part. This was discussed on UOS last
week (https://blueprints.launchpad.net/ubuntu/+spec/core-1411-systemd-
migration). The intention is to make this work on vivid first, and then
backport a newer L
13 matches
Mail list logo
