[lxc-devel] how are lxc-download images created?

Michael Adam obnox at samba.org
Fri Jan 16 09:29:41 UTC 2015


On 2015-01-15 at 18:30 -0500, Stéphane Graber wrote:
> On Fri, Jan 16, 2015 at 12:28:01AM +0100, Michael Adam wrote:
> > Hi,
> > 
> > How are the images that lxc-download uses created?
> > It would be great to have these recipes in the tree.
> > 
> > I am asking because apparently the fedora and debian
> > jessie images don't have the improvements/fixes for
> > running systemd as init that are installed when
> > using the lxc-debian or lxc-fedora template to
> > create the container (lxc.kmsg = 0 and lxc.autodev = 1).
> > 
> 
> They are built using the standard templates on
> jenkins.linuxcontainers.org using the scripts at github.com/lxc/lxc-ci.

Thanks! I am still in the process of really understanding what
happens there. It seems that these call the regular lxc-foobar
templates. But apparently, the download template creates the
config for the downloaded image, essentially including the
common config for the given distribution.

The problem here is that this does not take into account the
special configuration needed for e.g. Debian Jessie and
Fedora 15+ in order to make systemd happy. The debian and
fedora templates have customizations for the generated config
for this, but the common config is not conditional.
This means that the mentioned containers created by lxc-download
are not usable as is for me, but need some config changes first.

How can we circumvent that problem? Without replicating the logic
from the other templates inside the download template?
I generally see two thinkable approaches:

- have the creation mechanism package the config generated by
  the distri template and have the lxc-download template
  use that (possibly with slight modifications) instead the
  self-generated one.

- have version-specific default/common configs shipped instead
  of only distri-specific and have lxc-download use these.

Is there something else we can do?

Thanks - Michael
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.linuxcontainers.org/pipermail/lxc-devel/attachments/20150116/d3e6cb05/attachment.sig>


More information about the lxc-devel mailing list