Re: [lxc-users] UID > 65535 is not correctly mapped

2017-06-15 Thread Stéphane Graber
On Thu, Jun 15, 2017 at 08:00:48PM +0200, Matlink wrote: > Stéphane, I followed your howto, however, it didn't resolved my issue. > > I increased the size of the default map to one million, and did the > direct user/group mapping part: > > $ cat /etc/subuid > lxd:10:10 >

Re: [lxc-users] UID > 65535 is not correctly mapped

2017-06-15 Thread Matlink
Stéphane, I followed your howto, however, it didn't resolved my issue. I increased the size of the default map to one million, and did the direct user/group mapping part: $ cat /etc/subuid lxd:10:10 root:10:10 lxd:119373:1 root:119373:1 $ cat

Re: [lxc-users] UID > 65535 is not correctly mapped

2017-06-15 Thread Matlink
Stéphane made a post to anwser this : https://stgraber.org/2017/06/15/custom-user-mappings-in-lxd-containers/ Le 14/06/2017 à 16:41, Matlink a écrit : > > Hello community, > > I wanted to use GUI apps in my containers, I followed the great howto > here >

Re: [lxc-users] access to snapshots from within the containers

2017-06-15 Thread Stéphane Graber
On Thu, Jun 15, 2017 at 07:58:33AM +0200, mjansens wrote: > Hi, > > Thank you Stéphane for this clarification. > I'll indeed try to stick with the LTS version if I can. The snapshot glitch > has an easy work around: just need to do a ‘ls’ of the new snapshot contents > in the host (can even

Re: [lxc-users] LXD module for Cockpit?

2017-06-15 Thread Rick Leir
Mark, Stéphane, Quote from the cockpit site: "tasks such as starting containers, storage administration, network configuration". So it would be natural to integrate with LXD. For starters, it should support lxc's command line options, with the most commonly used options 'out in front' and the

Re: [lxc-users] snapshots of unprivileged containers belong to root

2017-06-15 Thread Jan Kowalsky
Hi all, after further investigation I realized that the difference was that the second container where it worked was with rootfs as btrfs subvol but the first one (copied from original container) wasn't. Ok, this explains the difference behaviour. And it comes even more obfuscating: The

Re: [lxc-users] access to snapshots from within the containers

2017-06-15 Thread Fajar A. Nugraha
On Thu, Jun 15, 2017 at 12:58 PM, mjansens wrote: > Where I might get stuck is in the network part: I will need at some point > to lock some containers in specific VLANs. I more or less have gathered > from various info on the web that LXD2.0.x networking is limited to