Comment 3 for bug 1784075

I was completely incorrect when I said this does not originate with Juju.

In environs/bootstrap/bootstrap.go, if there are no existing constraints for CPU power, CPU cores, memory or instance-type, this memory constraint is set.

It has always been done, and is intended to ensure that a sufficiently powerful instance is acquired on the regular clouds. For LXD it would simply have been ignored up until we began supporting constraints - now it is picked up.

We need to contrive some solution so that this is not done for LXD. In the interim, setting it high, or setting any value for CPU cores when specifying bootstrap constraints is a work-around.