Does juju setup memory quotas or other resource controls for LXD containers when deploying using the MAAS (or other) providers?
It does using the --constraints syntax on the lxd containers. This is new in 2.4.1 and 2.5.
Thanks. Is that documented anywhere? Is there a way to see, in a model, what juju thinks the constraints are for a given container?
There’s notes in the docs around lxd and constraints.
There’s the reference on which ones are not supported on what clouds:
There’s also the general using constraints docs:
It was noted in the release notes but being a point release was a bit sneaky.
To see the constraints of a given container they’re shown as part of the machine output. Use juju show-machine against a container to see what’s set. It’s the consistent details of any machine in question.