Comment 4 for bug 1844937

@chris.sanders, this sounds like an unintended consequence of the lxd profiles provided by charms work. See if you can reproduce by restarting the juju machine agent of the machine one of these lxd containers lives on: machine 3 if the container is 3/lxd/0. Set the logging level first:
  juju model-config logging-config='<root>=DEBUG;unit=DEBUG;juju.worker.instancemutater=TRACE'
Please provide the /var/log/juju/machine-#.log from the machine whose agent was restarted.

When a machine agent starts, it checks that the juju created containers are using the expected lxd profiles and that's it. I'm surprised that the default lxd profile isn't being added back. Though that could be a race between what the machine agent is trying to do, and the delay in autostart changes in the actual profile you've applied.

What scenario are you working towards with these lxd profile changes?