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
> r
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 /etc
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
> https://blog.simos.info/how-to-run-graphi
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 hap
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
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 conaitain