Comment 2 for bug 1685782

So I have the feeling we've always had a bug wrt containers accidentally inheriting the space from their host machine. However, in 2.0 we ignored space constraints for containers. In 2.1 we explicitly try to put containers into the spaces that you've asked for.

On AWS we are unable to get IP addresses and configure host machines to allow containers to share in the same space as the host machine, so they are actually effectively only in the "" (unnamed/unknown) space.

It should be possible to do:
  juju deploy host-aap --bind space
  juju deploy container-app --to lxd:MACHINE --bind ""

We may have to play around with syntax, as empty strings need to be interpreted at the right time.

In a bundle it would look like

  app:
    bindings:
      "": ""

I believe.

Or as a machine constraint:

  juju deploy foo --constraints 'space=""'