You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a nice post. It's a bit intrusive for the playbook to be changing the default address pool.
Although.. I guess that if the playbook is managing your Docker installation (which is optional and some may decide to turn it off), it may as well do some reconfiguration as it sees fit.
I suppose networks that had already been created will not be affected.. they'd need to be recreated to become small.
Or worse yet.. the new Docker pool definition (with the tiny networks) may be in conflict with the existing large ones.. and we'd need to force-delete them first and recreate them.
There are many things to figure out, but.. it seems like it's a possibility we should research.
The text was updated successfully, but these errors were encountered:
Ref: https://straz.to/2021-09-08-docker-address-pools/
This is a nice post. It's a bit intrusive for the playbook to be changing the default address pool.
Although.. I guess that if the playbook is managing your Docker installation (which is optional and some may decide to turn it off), it may as well do some reconfiguration as it sees fit.
Then the question is.. how do we do this nicely? It seems like the ansible-role-docker role we're currently using has some
docker_daemon_options
variable, which influences/etc/docker/daemon.json
.So.. we may be able to set some options.
I suppose networks that had already been created will not be affected.. they'd need to be recreated to become small.
Or worse yet.. the new Docker pool definition (with the tiny networks) may be in conflict with the existing large ones.. and we'd need to force-delete them first and recreate them.
There are many things to figure out, but.. it seems like it's a possibility we should research.
The text was updated successfully, but these errors were encountered: