Thanks for reporting this bug.
I see the message too. Of course the failure to unmount swap is a good
thing :) I'll assume the real bug, as perceived, is that the container
thinks it has something to swapoff. Fixing that will require /proc
contents filtering.
We can use the apparmor policy to deny read access to /proc/swaps, which
replaces the error with
/etc/rc0.d/S35networking: 61: /etc/rc0.d/S35networking: cannot open
/proc/swaps: Permission denied
* Deactivating swap... [ OK ]
Another possibility of course is for /etc/rc0.d/S35networking to detect
it is in a container and not try to swapoff.
However, as no harm is being done to the container or the host, I"m
going to mark this wishlist for now.
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
** Changed in: lxc (Ubuntu)
Importance: Undecided => Low
** Changed in: lxc (Ubuntu)
Importance: Low => Wishlist
--
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/930652
Title:
lxc & swapoff: Not superuser
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/930652/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
