Moin, I think cloud-init won't fit here, and maybe expose a critical part of my configuration.
To be more specific those LXD containers are unprivileged - so there is no mount inside those containers. I want to create one container with mount/"disk" /path/A-master/ and others mounting (with disk-device) /path/A-master/B-$containername/ Those folders might hold containerspecific security material, so they have to be unable to mount other directories than their own directory. MfG MonkZ Am 24.03.2017 um 08:30 schrieb Jamie Brown: > Hi, > > I’m first going to admit I don’t know the answer to your specific question, > though it’s not something I’ve come across. > > I’d suggest cloud-init (which is supported by lxd and assignable to profiles) > may be more appropriate for this? > https://cloudinit.readthedocs.io/en/latest/ > > Jamie > > On 22/03/2017, 10:31, "lxc-users on behalf of MonkZ" > <[email protected] on behalf of [email protected]> > wrote: > > Hi, > > is it possible to create a profile that has container specific > variables/macros? > > like: > > devices: > specific-share: > path: /srv/$CONTAINERNAME-share/ > source: /var/lib/lxd/storage-pools/lxd/custom/share/$CONTAINERNAME/ > type: disk > > Regards > MonkZ > > > > _______________________________________________ > lxc-users mailing list > [email protected] > http://lists.linuxcontainers.org/listinfo/lxc-users >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ lxc-users mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-users
