I agree that this shuffling around is not pretty, but we need a solution that makes 10.0.0.0/16 routable in cloud images where lxc/lxd are not in use as had prior to http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/ubuntu.wily/revision/2360
The current situation conflicts with how clouds are instructing users to set up private networks. [1] [2]
[1] http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Subnets.html [2] https://azure.microsoft.com/en-us/documentation/articles/virtual-networks-reserved-private-ip/
I agree that this shuffling around is not pretty, but we need a solution that makes 10.0.0.0/16 routable in cloud images where lxc/lxd are not in use as had prior to http:// bazaar. launchpad. net/~ubuntu- core-dev/ ubuntu- seeds/ubuntu. wily/revision/ 2360
The current situation conflicts with how clouds are instructing users to set up private networks. [1] [2]
[1] http:// docs.aws. amazon. com/AmazonVPC/ latest/ UserGuide/ VPC_Subnets. html /azure. microsoft. com/en- us/documentatio n/articles/ virtual- networks- reserved- private- ip/
[2] https:/