On Fri, Dec 11, 2015 at 12:20 PM, Dan Kegel wrote:
> Came back to this because it hit me again (14.04 host, 15.10 guest this
> time).
> I actually don't need to be able to write to /proc/sys/kernel/sem
> from inside the container; I just need its limits to be high enough.
>
> $ uname -a
> Linux d
Came back to this because it hit me again (14.04 host, 15.10 guest this time).
I actually don't need to be able to write to /proc/sys/kernel/sem
from inside the container; I just need its limits to be high enough.
$ uname -a
Linux dank-desktop 3.13.0-66-generic #108-Ubuntu SMP Wed Oct 7
15:20:27 U
In my LXC Ubuntu 14.04 server, I was trying to run
apt-get -f install
and found out that I cannot erase or create any file under /usr/sbin
other dirs like /usr/bin are find
The subdir /usr/sbin has identical atttributes to /usr/sbin in other
servers, but it still does not work.
This messed up my u
On 12/09/2015 06:43 PM, Serge Hallyn wrote:
Ok, systemd does behave differently if it shouldn't be able
to create devices. If you add
lxc.cap.drop = mknod sys_rawio
to your configs does that help?
This did not help. I took it a step further and did an install with the
lxc capabilities c
And the same is true for the original wily container from the official image:
david@kimera:~$ lxc stop wily
david@kimera:~$ lxc profile apply wily default,debug_init
Profile default,debug_init applied to wily
david@kimera:~$ lxc start wily
david@kimera:~$ time lxc exec wily /bin/bash
root@wily:~#
