[Lxc-users] clones of clones are failing to start

[Jäkel, Guido]

Dear Serge,

to assist to avoid such problems i would propose to introduce macro expansion (of the own tags but also by incorporating the environment variables) into the configuration argument parser and to provide some useful basics like the container name.  Then one may use e.g.

	lxc.hook.mount = $MYCONTAINER_HOME/hooks/$lxc.name

In my personal LXC framework I need this because I want to have abstract configuration files for classes of containers. I simulate this by preparsing additional configuration files and converting it to "-s" options for lxc-start

It would be also helpful, if one may use the -f option more than once (, don't checked if this is not already possible) and if there is a meta tag to use inside a configuration file to include another ('lxc.include = foo' or '@INCLUDE foo').

Guido

>-----Original Message-----
>From: Serge Hallyn [mailto:serge.hallyn at ubuntu.com]
>Sent: Wednesday, July 17, 2013 11:32 PM
>To: Jay Taylor
>Cc: lxc-users
>Subject: [Spam-Wahrscheinlichkeit=94]Re: [Lxc-users] clones of clones are failing to start
>
>clearly the updating of hostnames should always exempt lxc.cap.drop,
>and a few other lines.  Just how robust we can make this I'm not 100%
>sure.  (I.e. in a lxc.hook.mount = /opt/mycontainer/hooks/mycontainer.1,
>how can we know which 'mycontainer' strings should be replaced?)
>