Admittedly juju deploy fails in 1.20.6 if lxc-clone-auf is set to true. However it works in the latest development version.
BUT:
The latest development version fails to deploy if there is a leftover container that failed to start in the previous deploy (say using juju version 1.20.6). Because juju fails to destroy a container that failed to start.
FIX:
Use lxc-destroy to clean up the leftover containers.
Looking into fixing this issue in the code. A question that pops to mind is why are we reusing containers anyway.
Admittedly juju deploy fails in 1.20.6 if lxc-clone-auf is set to true. However it works in the latest development version.
BUT:
The latest development version fails to deploy if there is a leftover container that failed to start in the previous deploy (say using juju version 1.20.6). Because juju fails to destroy a container that failed to start.
FIX:
Use lxc-destroy to clean up the leftover containers.
Looking into fixing this issue in the code. A question that pops to mind is why are we reusing containers anyway.
Thank you for you patience..