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 Jul 22, 2022. It is now read-only.
'By default, a container will have an IP address assigned automatically out of the pool of available IP addresses: 10.40.0.1 - 10.47.255.254. Once a container is recreated, it may receive different IP address. A container does not change an IP address if it is restarted.' I know it's docker's fault as well, but ew.
The text was updated successfully, but these errors were encountered:
I think that would not be possible without the support from weavenet. And I believe they would not consider to add this feature because these are the IP addresses of the cluster's VPN maintained by weavenet. It has got enough big IP range for the largest deployments in the world :) Could you please elaborate more on the motivation for this feature?
'By default, a container will have an IP address assigned automatically out of the pool of available IP addresses: 10.40.0.1 - 10.47.255.254. Once a container is recreated, it may receive different IP address. A container does not change an IP address if it is restarted.' I know it's docker's fault as well, but ew.
The text was updated successfully, but these errors were encountered: