That makes sense. Building VM images is what I ended up doing, and it worked. I wonder if there would be a way for `autopkgtest-build-lxd` to provide a more clear error or warning message when attempting to build an incompatible image? Based on the error messages, it initially looked to me more like a transient error, so I went down a wrong path for a while, retrying, trying to restart lxd, etc. Even if this isn't generally feasible (e.g. if using custom images or a custom kernel), I imagine most mistakes like mine could be caught with some simple logic based on the name of the image when using the official Ubuntu remote? No idea if that is a reasonable approach; it's just an idea. Thanks for your help!
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2146949 Title: autopkgtest-build-lxd times out for xenial image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2146949/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
