Not sure whether this is a known issue (perhaps something I should have just “known” as a Linux server admin), but figured I’d share in case someone else runs into the same issue.
I copied a live system (VMware VM in this case) via lxd-p2c like so:
$ sudo ./lxd-p2c https://lxd1.example.com wordpress-test / /boot
and ended up with a container which has the contents of ‘/’ and ‘/boot’. That part worked.
/etc/fstab file in the newly generated container still has the mount points from the old system. At boot time, the entry within the
/etc/fstab time in the container were enough to cause the network configuration to not be applied as expected. Once I commented out the entries within the /etc/fstab file and restarted the container, the system was able to pull an IP Address via DHCP as intended.
On a related note:
After very brief testing, I was able to have the container start without issue without a /etc/fstab file present. Is that file even needed within a LXD container? I assume it is, but very quick testing appears to indicate otherwise. Would an empty /etc/fstab file cause any issues?