I wouldn't say you are in for a world of hurt but you'll have to accept that the package will periodically update and in the process kill your containers/vms. My primary objections to snapd are:
1) updates are pushed/applied and services restarted on an arbitrary schedule which means you can't test updates prior to rolling them out or otherwise control when a service is taken offline by an update
2) snapd doesn't log to standard OS logging facilities and the logs it does have are cleared after 72 hours
3) snapd pollutes home directories with a directory called "snap"
snapd is a poorly conceived project written by people that are profoundly ignorant of how real services and servers are actually operated. Despite having the above flaws repeatedly pointed out, the developers have shown zero interest in taking actual concrete actions to address them.
Build LXD yourself. It is not that complicated if one updates go to something beyond 1.14. Only downside is that you may need to create your own init scripts and a lxd group, but that's not complicated either.
1) updates are pushed/applied and services restarted on an arbitrary schedule which means you can't test updates prior to rolling them out or otherwise control when a service is taken offline by an update
2) snapd doesn't log to standard OS logging facilities and the logs it does have are cleared after 72 hours
3) snapd pollutes home directories with a directory called "snap"
snapd is a poorly conceived project written by people that are profoundly ignorant of how real services and servers are actually operated. Despite having the above flaws repeatedly pointed out, the developers have shown zero interest in taking actual concrete actions to address them.