Hi,
I am still having problems with the containers. Although i am able to
launch and instantiate a container when i disable the apparmor, however
the new instantiated container is missing the /proc filesystem as a
result I am unable to do any meaningful operations (e.g., ping
opeation).
I am runn
@Serge, thanks a lot it worked!
--
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/947617
Title:
After update, lxc does not start
To manage notifications about this bug go to:
https://bugs
@Alan,
your container is not allowed to mount /proc because of the apparmor
profile. The easiest way around this is to disable apparmor for that
container, by edigint /var/lib/lxc/(containername)/config and
uncommenting the line:
#lxc.aa_profile = unconfined
--
You received this bug notificati
Not sure if my issue is related to this. I migrate a container to a new
machine. I have been able to start it... but inside it, I can't use pbuilder,
which is used to create multiple environments to build debian packages. Getting
this message:
aboudreault@packages:~$ pbuilder-dist precise amd64
@janevert,
yes that should be fixed. I've opened bug 1010598 to track that.
Thanks.
--
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/947617
Title:
After update, lxc does not start
To m
Serge,
This container I created with oneiric with the lxc-sshd template. It worked
there reasonably well (only needed to add a default route, which is missing).
I've compared (visually) what oneiric created for mounting and what precise
would have created. It seems there is only 1 difference. One
@janevert,
it looks like you have some custom mounting going on. Making a custom
profile would be the best way around it, otherwise disabling apparmor as
you've done obviously works too.
The ubuntu server guide (for 12.04) lxc section shows how to create and
use a custom profile. It also might
After the workaround, my container is running.
--
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/947617
Title:
After update, lxc does not start
To manage notifications about this bug go t
For me this seems not fixed.
ii apparmor 2.7.102-0ubuntu3 User-space
parser utility for AppArmor
ii lxc 0.7.5-3ubuntu56 Linux
containers userspace tools
root@kira:~# lxc-start -n jake
lxc-start: failed to mount rootfs
lx
This bug was fixed in the package apparmor - 2.7.100-0ubuntu1
---
apparmor (2.7.100-0ubuntu1) precise; urgency=low
* New upstream bug fix release which fixes (in addition to other bugs):
- LP: #940362
- LP: #947617
- LP: #949891
* Drop the following patches, included u
** Also affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Changed in: apparmor (Ubuntu)
Status: New => In Progress
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => John Johansen (jjohansen)
** Changed in: apparmor (Ubuntu)
Milestone: None => ubun
I pushed a minimal change to LXC disabling the apparmor profile for now.
Instead of removing the profile or using aa-disable I simply changed the path
to /usr/bin/lxc-start to /usr/bin/lxc-start.disabled in the profile, whenever
apparmor is fixed we'll just need to add the mount statements, bump
This bug was fixed in the package lxc - 0.7.5-3ubuntu33
---
lxc (0.7.5-3ubuntu33) precise; urgency=low
* Update apparmor profile to temporarily disable it.
This will be reverted once apparmor has been fixed. (LP: #947617)
-- Stephane GraberTue, 06 Mar 2012 12:25:21 -0500
*
Quoting Stéphane Graber (stgra...@stgraber.org):
> I'm happy to update our apparmor profile as soon as apparmor stops
> crashing :)
>
> For now, the only way I found to get containers working again is to turn
> off the apparmor profile.
Yikes.
It sounds like temporarily disabling the apparmor pr
@stgraber,
I hope you don't mind I've assigned this to you, as you were looking at
it yesterday, and I'm out until next monday.
I marked it high priority, because it will hit a lot of people. But on
the other hand there *is* a workaround, so I guess the priority should
be dropped... But I'll le
I'm happy to update our apparmor profile as soon as apparmor stops
crashing :)
For now, the only way I found to get containers working again is to turn
off the apparmor profile.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ub
Seems it's a mistake in /etc/apparmor.d/usr.bin.lxc-start
Don't know how to fix it, but if you want to make lxc work quickly (without
apparmor):
ln -s /etc/apparmor.d/usr.bin.lxc-start
/etc/apparmor.d/disable/usr.bin.lxc-start
service apparmor restart
lxc-start ..
--
You received this bug n
This is what I'm seeing with dmesg:
[16241.285998] type=1400 audit(1331004691.503:33): apparmor="DENIED"
operation="mount" parent=9376 profile="/usr/bin/lxc-start"
name="/usr/lib/lxc/root/" pid=9387 comm="lxc-start"
src_name="/var/lib/lxc/u1-server/rootfs/" flags="rw, rbind
--
You received this
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/947617
Ti
--
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/947617
Title:
After update, lxc does not start
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc
20 matches
Mail list logo
