Debian – LXD 2.0 on Debian 8.4

The later release (non-beta) of lxd (v2.0) seems to have resolved my issue. The steps, which may be found in the excellent documentation here, are:

1. Publish an image (without stopping the container) on host A;

   $ lxc publish --force container_name --alias image_name
   Container published with fingerprint: d2fd708361...a125d0d5885
   

2. Export the image to a file;

   $ lxc image export image_name 
   Output is in dd2fd708361...a125d0d5885.tar.gz
   

3. Copy the file to host B, and import;

   $ lxc image import dd2fd708361...a125d0d5885.tar.gz --alias image_name
   Transferring image: 100%
   

4. Launch the container (from the image) on host B;

   $ lxc launch image_name container_name
   Creating container_name
   Starting container_name
   

In some instances the publish command may lead to a split xz tar-ball --- but both formats are supported. Simply import the meta-data and rootfs components with

    lxc image import <metadata tarball> <rootfs tarball> --alias image_name

1. If your LXD host is actually a virtual machine, ensure that the virtual machine's network adaptor is configured to promiscuous mode, so that way LXD container traffic passes from the physical to the virtual network.
2. Set a static IP address in the lxd container(s), because DHCP (from your physical gateway) doesn't seem to work.

In my 6th edit I said that I needed to manually add a default route in the container, but that's not true. I only needed to do that because I forgot to specify the gateway LAN IP address in the /etc/network/interfaces file. So it's not an LXD issue, just don't forget to specify it.