Is there a way to have a bridge network for persistent containers?

[paulomorgado]

I have a constrained developer environment where containers are required to always be on a bridge network.

[davidfowl]

cc @danegsta

[danegsta]

The main reason why we haven’t taken advantage of persistent networks yet is that Docker’s default network address assignments are extremely broad (/20 subnets) such that only about 30 simultaneous networks can exist without exhausting the default available pool, so every network we leave running risks hitting network limits for heavy users. That being said, it’s definitely something we want to support.

[paulomorgado]

You could leave the up to the user explicitly set.

I prefer extra work to "you can't do that here".

[danegsta]

We would definitely give users the ability to control network address allocation, but we also need to be careful how we roll out features with a high likelihood of failure for the average user. Maybe we should consider an experimental API as a stopgap while we solve for the default experience.

[paulomorgado]

Maybe we should consider an experimental API as a stopgap while we solve for the default experience.

Definitely!

[danegsta]

We've just merged the initial support for running a persistent network when there are persistent containers in an app host.