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
{{ message }}
This repository has been archived by the owner on Dec 11, 2020. It is now read-only.
I experience strange behavior that it tries to replace my docker network after rebooting the server.
Looks like the ipam_config stanza cannot be properly merged and then triggeres the replacement.
i fixed that by generating the gateway attribute at my own, not sure if this is an expected behavior as the documentation tells its an "optional" parameter.
I experience strange behavior that it tries to replace my docker network after rebooting the server.
Looks like the ipam_config stanza cannot be properly merged and then triggeres the replacement.
# module.base.docker_network.server must be replaced -/+ resource "docker_network" "server" { - attachable = false -> null check_duplicate = true driver = "bridge" ~ id = "f565f7f1a0db0c184f69c24e8f113ce7d88c12e43ae4bf862b0f51c15940a633" -> (known after apply) - ingress = false -> null ~ internal = false -> (known after apply) ipam_driver = "default" ipv6 = true name = "server-vagrant" ~ options = {} -> (known after apply) ~ scope = "local" -> (known after apply) - ipam_config { # forces replacement - aux_address = {} -> null - gateway = "172.16.10.1" -> null - subnet = "172.16.10.0/24" -> null } - ipam_config { # forces replacement - aux_address = {} -> null - gateway = "2001:1:6d:99f:400::1" -> null - subnet = "2001:1:006d:099f:0100:0000:0000:0000/80" -> null } + ipam_config { # forces replacement + subnet = "172.16.10.0/24" } + ipam_config { # forces replacement + subnet = "2001:1:006d:099f:0100:0000:0000:0000/80" } }
docker inspect after creation:
docker inspect after reboot:
The text was updated successfully, but these errors were encountered: