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
You'll see this error if you try to start a new network, i.e. maybe you ran a network named "warnet" previously but it has been shut down in some way that is NOT docker-compose down. Even though the containers may be stopped and deleted, the network may still exist and that occupies our subnet 100.....
The text was updated successfully, but these errors were encountered:
maybe, all new networks should use a unique subnet prefix. Then we'd have 0-255 possible networks (minus whatever prefixes like 10, 192, etc are "unroutable")
You'll see this error if you try to start a new network, i.e. maybe you ran a network named "warnet" previously but it has been shut down in some way that is NOT
docker-compose down
. Even though the containers may be stopped and deleted, the network may still exist and that occupies our subnet100....
.The text was updated successfully, but these errors were encountered: