model default network space does not apply to LXD containers

[Peter Matulis]

When I do this:

$ juju model-default default-space=public-space

I still get deploy errors like:

no obvious space for container "0/lxd/0", host machine has spaces: "public-space", "undefined"

[Ian Booth (wallyworld)]

model-default sets the default value for newly created models. It doesn't affect exiting models.

Did you mean to type model-config?

[Tim Penhey (thumper)]

Could you also please include the space definitions for the model? And what the deploy commands were?

[Joseph Phillips (manadart)]

At present the default-space configuration applies only to the space used for the default binding. It does not inform host interface bridging for containers.

I think the expectation that is does is reasonable though. We should address it.

[Peter Matulis (petermatulis)]

But confirm that `model-config` is the command to use here? It's confusing which one to use especially when the option itself is a type of default (like a default space).

[Joseph Phillips (manadart)]

Yes, model-config will do it. I noticed this was not documented, and added it to the docs here:
https://juju.is/docs/configuring-models

I'll amend when we address this ticket.

[Joseph Phillips (manadart)]

This can be done with the Dqlite spaces implementation.

It is not difficult - we can discuss in Riga.

[John A Meinel (jameinel)]

default-space shouldn't "apply to containers" but it *should* apply to the applications that would end up being deployed into containers.

At this point, we have a code path that we should probably remove that 'falls back to the alpha space' when doing automatic detection, that we should probably change to just refuse as all applications *must* have valid bindings.

[Nicolas Vinuesa (nvinuesa)]

For deployments, the bindings should be explicitly set. And for adding containers, space passed as constraints should do it.