More about "Support for daemonized app containers"?

[brauner (Christian Brauner)]

@osshelp

But nonetheless, i would appreciate any details on this from the first source (someone from dev team or docs on this feature).

Thanks.

Well, today’s your lucky day then since I’m the main developer/tech lead for liblxc and a core-developer and maintainer of LXD. Also, you’re referencing my patch.

@osshelp

But i was initially asking about technical details of this new feature.

For example, is there some docs or any other info how to get it working in case of LXC.

But that’s what I showed you. You can use it via lxc-execute or by directly using the API if you build your own tool.

@osshelp

For example, is there some docs or any other info how to get it working in case of LXC. At least where to get this new one “minimal-init”. Does it come with LXC 3.0 or …?

This minimal init has been shipping with LXC since 2008. It will be installed when you install LXC unless your distro of choice has explicitly refrained from packaging it.

@osshelp

And most important - is there any known issues or limitations on using this feature within containers under LXD management?

LXD currently does not support application containers run through this minimal init. If you only care about running a different binary as init withou the minimal-init then you can make it work with LXD right now:

lxc config set <container-name> raw.lxc "lxc.init.cmd= /bin/bash"

@osshelp

As i understood, it mostly about building your own “custom” image.

I don’t understand what you mean by this? LXD is a container-manager daemon sitting on top of liblxc/LXC which is a shared C library.