I have edited the my docker preferences in the advanced section, where you can paste in JSON and restart. I have added the below and the application never starts, it says to reset if it hangs (which I do) but gives me no cause as to why it hangs. checking the documentation my JSON looks valid.
config as per the below:
{ "experimental" : true, "bip" : "192.168.16.1/20", "debug" : true, "default-gateway" : "192.168.17.1", "dns" : [ "10.50.0.1" ], "fixed-cidr" : "192.168.17.0/24", "ip-forward": true } and the attached screen 
I've tried it with just the two settings it doesn't work still. I tried it with fixed-cidr on its own, it was accepted but the change didn't reflect in my image, the machine was still on its default 172.17.0.0/16
EDIT: ok settings have been accepted as per the below:
{ "experimental" : true, "bip" : "192.168.16.1/20", "debug" : true, "default-gateway" : "192.168.17.1", "dns" : [ "10.50.0.1" ], "fixed-cidr" : "192.168.17.0/24" } however the bridge is now not working, I cannot ping from my VM outside the VM network, do I need to do something additional to nat the new bridge (was a new bridge created when I did this or was the original edited?)
Thanks
1 Answers
Answers 1
There issue would seem to be with your usage of default-gateway. There are a few settings here that you need to set.
The default-gateway setting needs to be within the IP range being used for the default range. Now you did provide the fixed-cidr, however if you previously started dockerd with a different range, the docker0 bridge will still exist or even be created with the range it was originally created with.
If you provide a bip option this should clear it up, but note that the option needs to be within the range of your default-gateway. Also note the original configuration you posted is incorrect as you have the bip set to 192.168.1.5/24 but the gateway is 192.168.2.5 and the fixed-cidr is in that same range.
0 comments:
Post a Comment