Comment 3 for bug 2024907

The juju charm lxd profile work was implemented well before juju supported vm's via lxd, thus does not distinguish. Looks this needs to be investigated.

There is no expectation in the juju lxd profile implementation that a container may require a reboot. In fact it's not something that we'd want to do. Charms with lxd profiles can be deployed to a new or existing lxd container at any time with no guarantee that it has no other units running on it.