Re: [lxc-users] setcap capabilities

2016-02-29 Thread Serge Hallyn
Quoting Mark Constable (ma...@renta.net): > FWIW another package that requires setcap. This is the first one I've seen > that falls back to setuid OOTB. > > Setting up mtr-tiny (0.86-1) ... > Failed to set capabilities on file `/usr/bin/mtr' (Invalid argument) > The value of the capability argumen

Re: [lxc-users] setcap capabilities

2016-02-28 Thread Mark Constable
FWIW another package that requires setcap. This is the first one I've seen that falls back to setuid OOTB. Setting up mtr-tiny (0.86-1) ... Failed to set capabilities on file `/usr/bin/mtr' (Invalid argument) The value of the capability argument is not permitted for a file. Or the file is not a

Re: [lxc-users] setcap capabilities

2016-02-18 Thread Serge Hallyn
Quoting Mark Constable (ma...@renta.net): > On 19/02/16 12:21, Serge Hallyn wrote: > Unpacking systemd (229-1ubuntu2) over (228-5ubuntu3) ... > dpkg: error processing archive > /var/cache/apt/archives/systemd_229-1ubuntu2_amd64.deb (--unpack): > unable to make backup link of './b

Re: [lxc-users] setcap capabilities

2016-02-18 Thread Mark Constable
On 19/02/16 12:21, Serge Hallyn wrote: Unpacking systemd (229-1ubuntu2) over (228-5ubuntu3) ... dpkg: error processing archive /var/cache/apt/archives/systemd_229-1ubuntu2_amd64.deb (--unpack): unable to make backup link of './bin/systemctl' before installing new version: Operation not permit

Re: [lxc-users] setcap capabilities

2016-02-18 Thread Serge Hallyn
Quoting Mark Constable (ma...@renta.net): > On 19/02/16 11:39, Serge Hallyn wrote: > echo 0 > /proc/sys/fs/protected_hardlinks > >> > >>Thanks for the response Serge but this "problem" all but makes unpriv > >>containers (xenial at least) unusable. Todays example... > >> > >>Unpacking systemd (

Re: [lxc-users] setcap capabilities

2016-02-18 Thread Mark Constable
On 19/02/16 11:39, Serge Hallyn wrote: echo 0 > /proc/sys/fs/protected_hardlinks Thanks for the response Serge but this "problem" all but makes unpriv containers (xenial at least) unusable. Todays example... Unpacking systemd (229-1ubuntu2) over (228-5ubuntu3) ... dpkg: error processing archiv

Re: [lxc-users] setcap capabilities

2016-02-18 Thread Serge Hallyn
Quoting Mark Constable (ma...@renta.net): > On 19/02/16 02:32, Serge Hallyn wrote: > but inside a container I get... > > ~ /sbin/setcap cap_net_bind_service=+ep /usr/bin/caddy > Failed to set capabilities on file `/usr/bin/caddy' (Invalid argument) > >>> > >>>If not in a user names

Re: [lxc-users] setcap capabilities

2016-02-18 Thread Serge Hallyn
Quoting Mark Constable (ma...@renta.net): > On 19/02/16 02:32, Serge Hallyn wrote: > >># for containers to allow suid exec > >>echo 0 > /proc/sys/fs/protected_hardlinks > >> > >>on the host but that is going to be awkward for folks who do not happen > >>to know this "trick" meaning generally trying

Re: [lxc-users] setcap capabilities

2016-02-18 Thread Mark Constable
On 19/02/16 02:32, Serge Hallyn wrote: but inside a container I get... ~ /sbin/setcap cap_net_bind_service=+ep /usr/bin/caddy Failed to set capabilities on file `/usr/bin/caddy' (Invalid argument) If not in a user namespace, ... well it works for me, but you may have to edit the files under /u

Re: [lxc-users] setcap capabilities

2016-02-18 Thread Mark Constable
On 19/02/16 02:32, Serge Hallyn wrote: # for containers to allow suid exec echo 0 > /proc/sys/fs/protected_hardlinks on the host but that is going to be awkward for folks who do not happen to know this "trick" meaning generally trying to install the courier-mta package on unpriv containers is go

Re: [lxc-users] setcap capabilities

2016-02-18 Thread Serge Hallyn
Quoting Mark Constable (ma...@renta.net): > On 14/02/16 03:20, Serge Hallyn wrote: > >>but inside a container I get... > >> > >>~ /sbin/setcap cap_net_bind_service=+ep /usr/bin/caddy > >>Failed to set capabilities on file `/usr/bin/caddy' (Invalid argument) > > > >If not in a user namespace, ... we

Re: [lxc-users] setcap capabilities

2016-02-13 Thread Mark Constable
On 14/02/16 03:20, Serge Hallyn wrote: but inside a container I get... ~ /sbin/setcap cap_net_bind_service=+ep /usr/bin/caddy Failed to set capabilities on file `/usr/bin/caddy' (Invalid argument) If not in a user namespace, ... well it works for me, but you may have to edit the files under /u

Re: [lxc-users] setcap capabilities

2016-02-13 Thread Serge Hallyn
Quoting Mark Constable (ma...@renta.net): > Outside a container on the host I can... > > ~ /sbin/setcap cap_net_bind_service=+ep /usr/bin/caddy > ~ getcap /usr/bin/caddy > /usr/bin/caddy = cap_net_bind_service+ep > > but inside a container I get... > > ~ /sbin/setcap cap_net_bind_service=+ep /us