Lxc copy now starts on destination behavior change 3.12 -> 3.13

(Trystan) #1

lxc copy --refresh --stateless (or sans --stateless) container server:container is now starting the destination container even with boot.autostart=false.

Just a warning for anyone with automatic lxc copy scripts

(Stéphane Graber) #2

Hmm, that sounds like a bug and I seem to be getting here too, trying to figure out what’s going on.

(Stéphane Graber) #3

Not sure why we didn’t see this before as the code that caused it was supposedly there since late 2017…