Comment 7 for bug 1836226

> Why does this profile get validated even when it's not being deployed [to lxd]?

@pjds, because Juju doesn't know if the charm is going to be deployed to lxd on one of your non-lxd cloud machines in the future. To expand on @jam's comment 1, let's say you have 2 machines in AWS. If Juju allowed this deployment to machine 1 without --force:

juju deploy naughty-charm --to 1

What should it do when you add another unit of that charm to a lxd container on AWS machine 2?

juju add-unit naughty-charm --to lxd:2

Today --force is only available during deploy, so that's when Juju validates the profile; it barks at all clouds because of the '--to lxd' potential. In the future, @rick_h and @jam are proposing to move that validation closer to the lxd-specific problem areas. I think it's a terrific idea, fwiw.