lxc: pull in networking and templates via RRECOMMENDS

The lxc recipe ships three sub-packages: ${PN}, ${PN}-networking, and
${PN}-templates. ${PN} contains the lxc-* command-line binaries.
${PN}-networking owns lxc-net.service, /etc/default/lxc-net, the
dnsmasq drop-in for the lxcbr0 bridge, and the firewall plumbing.
${PN}-templates owns /usr/share/lxc/templates, the per-distro
container-creation scripts that lxc-create invokes via --template.

Installing only the main ${PN} package leaves a non-functional LXC.
There's no lxcbr0 bridge, so any container whose config references it
(every download-template default config does) fails to start with

  network.c: netdev_configure_server_veth: Failed to attach "vethXXX"
             to bridge "lxcbr0", bridge interface doesn't exist

and there are no template scripts, so lxc-create --template <foo>
has nothing to invoke. The user-facing toolchain is effectively broken
unless the integrator knows to add the sub-packages by hand.

Pull both sub-packages in through RRECOMMENDS so any image that
installs lxc gets a functional LXC by default, regardless of whether
the install path is packagegroup-lxc, IMAGE_INSTALL:append, or
CORE_IMAGE_EXTRA_INSTALL. Integrators who don't want them (custom
networking, hand-written templates) can drop either or both through
BAD_RECOMMENDATIONS.

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>

0 files changed, 0 insertions, 0 deletions