Goals
- allow networks created with
--config-from to not be considered "dangling" when running docker system prune
- associate
--config-from networks to the service stack they are used in
Description
Currently, when I create a local bridge network on each of my swarm nodes using --config-only, those networks are not removed with docker system prune. However, when I create the actual swarm network with --config-from, that network is removed with docker system prune. Having the ability to define a config-from network in the swarm compose file that is related to the service stack would be helpful, and I would assume would also prevent it being considered a dangling network.
From what I have found, there is no configuration option for --config-from in docker-compose files. It would be nice to have a flag under .network.<network-name>.ipam.config, such as .network.<network-name>.ipam.config.config-from:
[...]
networks:
my-network:
ipam:
config:
- config-from: my-local-node-network
Related: #49, #605, #407
Goals
--config-fromto not be considered "dangling" when runningdocker system prune--config-fromnetworks to the service stack they are used inDescription
Currently, when I create a local bridge network on each of my swarm nodes using
--config-only, those networks are not removed withdocker system prune. However, when I create the actual swarm network with--config-from, that network is removed withdocker system prune. Having the ability to define aconfig-fromnetwork in the swarm compose file that is related to the service stack would be helpful, and I would assume would also prevent it being considered a dangling network.From what I have found, there is no configuration option for
--config-fromin docker-compose files. It would be nice to have a flag under.network.<network-name>.ipam.config, such as.network.<network-name>.ipam.config.config-from:Related: #49, #605, #407