*** This bug is a duplicate of bug 1296459 ***
https://bugs.launchpad.net/bugs/1296459
I believe this issue was solved with apparmor 2.8.95~2430-0ubuntu3. It
contains a fix for a regression in how apparmor_parser generates
AppArmor policy containing mount rules.
I'm going to mark this bug as
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/1294284
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) = Tyler Hicks (tyhicks)
** Changed in: lxc (Ubuntu)
Milestone: None = ubuntu-14.04
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
I may have solved the problem after re-installing the server.
Before upgrading to 14.04 I made sure to check if Ubuntu Saucy container
starts and it did. Then I upgraded to 14.04 and created new Ubuntu
Trusty container. Both Saucy and Trusty containers started properly,
although both output some
I created new container with the command you suggested, same results as
original Ubuntu container I created.
Here's trace output.
lxc-start 1395236983.307 INFO lxc_start_ui - using rcfile
/var/lib/lxc/ubuntu/config
lxc-start 1395236983.309 WARN lxc_log - lxc_log_init called
Thanks for the info. Really this sounds like a bug in upstart - the lxc
startup all goes fine.
If you chroot into the container, does that go all right?
sudo chroot /var/lib/lxc/ubuntu/rootfs
** Changed in: lxc (Ubuntu)
Status: Incomplete = New
--
You received this bug notification
Yeah, I can use chroot without issues.
--
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/1294284
Title:
LXC Ubuntu containers do not start in Ubuntu 14.04
To manage notifications about
Please install strace in the container
sudo chroot /var/lib/lxc/ubuntu/rootfs apt-get install strace
and then strace init:
sudo lxc-start -n ubuntu -- /usr/bin/strace /sbin/init
Also, does
sudo lxc-execute -n ubuntu -- /bin/bash
work?
--
You received this bug notification
lxc-execute appears to work, but it does output two errors.
lxc-execute: Device or resource busy - failed to set memory.use_hierarchy to 1;
continuing
lxc-execute: Device or resource busy - failed to set memory.use_hierarchy to 1;
continuing
And here's the output from strace:
lxc-start:
Please show the output of
sudo lxc-start -n ubuntu -- /sbin/init --debug --verbose
--
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/1294284
Title:
LXC Ubuntu containers do not start in
Syslog attached.
** Attachment added: syslog
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1294284/+attachment/4032651/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
lxc-start: Device or resource busy - failed to set memory.use_hierarchy to 1;
continuing
lxc-start: Device or resource busy - failed to set memory.use_hierarchy to 1;
continuing
6init: Handling startup event
6init: mountall goal changed from stop to start
6init: mountall state changed from
apport information
** Tags added: apparmor apport-collected trusty
** Description changed:
I have a testing server which I installed Ubuntu 13.10 and then upgraded
to Ubuntu 14.04 beta using do-release-upgrade -d. I do not have the
option to create clean install with 14.04 directly as
Does the problem go away when you add the line
lxc.aa_profile = unconfined
to /var/lib/lxc/ubuntu/config?
your kern.log has a lot of deniels for filesystem mounts which should be
allowed, like mounting /sys.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Meminfo attached.
** Attachment added: meminfo
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1294284/+attachment/4032652/+files/meminfo
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
As a matter of fact, even if I stop the apparmor service it doesn't
change the problem with Ubuntu containers.
--
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/1294284
Title:
LXC Ubuntu
Added the line but no change.
--
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/1294284
Title:
LXC Ubuntu containers do not start in Ubuntu 14.04
To manage notifications about this bug
Nevermind, just saw that Serge already asked you to do this...
--
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/1294284
Title:
LXC Ubuntu containers do not start in Ubuntu 14.04
To
Hmm, this is really quite weird...
Can you try:
- lxc-create -t download -n p1 -- -d ubuntu -r trusty -a amd64
- lxc-start -n p1
I want to know whether the issue is related to your rootfs or related to
the host, that should tell us.
--
You received this bug notification because you are a
Please run
apport-collect 1294284
and attach /var/log/syslog (after making sure no sensitive information
like usernames and passwords are there).
Please also show the contents of /proc/meminfo. It seems like services
are starting fine and then being killed, which sounds like the OOM
killer.
I never showed the results for the u1 container as they were identical
to ubuntu.
--
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/1294284
Title:
LXC Ubuntu containers do not start in
Just to be sure - I had used 'lxc-create -t download -n u1' but your
results showed a container name 'ubuntu'. Did you use '-n u1' or '-n
ubuntu when creating the new container?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in
Ok, desperate times call for desperate measures... can you do the following:
- sudo apt-get install debsums procenv
- sudo debsums -sa and attach the output to this bug report
- sudo procenv and attach the output to this bug report
--
You received this bug notification because you are a
Output you requested attached.
** Attachment added: output.txt
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1294284/+attachment/4032814/+files/output.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Thanks for reporting this bug. This is definately very odd.
If you create a container with
sudo lxc-create -t download -n u1 -- -d ubuntu -r trusty -a amd64
sudo lxc-start -n u1
does that container start fine?
Can you do
sudo lxc-start -n ubuntu -l trace -o debug.out
then kill the
25 matches
Mail list logo
