A new project, you need to run docker local environment, configuration finished, everything is normal. After a few hours on various projects being given, then all can not be used, the investigation down, the project turned out to be even consul overtime, leading to follow-up all go elsewhere
Then the consul to see what the problem, see the process in the docker
docker ps -a
See the consul is up state, it is normal
Strange, consul is normal ah, why the project even consul overtime? 127.0.0.1:8500 try to access the browser, is actually round and round forever, not open. The problem arises here
Since docker watching is normal, the browser can not access. They reflect a problem? However, just the start, everything is normal, otherwise the project would not run for a few hours
Programming for Google, search out things have not seen what's useful information
Time has passed for two hours, but unfortunately, only the most primitive way - "restart" to temporarily solve the problem, first use docker restart dev-consul to restart the container, the container was found that up, but still can not access the browser ; and then delete the container, and then re-run of the container, or not; finally, had to restart the computer, and the magic is, restart the computer, start the container actually really everything is normal
Originally thought things come to an end, which know, after a few hours, they encountered the same problem: the project has a variety of error, even consul timeout. Will now know that this is a problem, it can not avoid, we must solve
Try to find the operation and maintenance to help me look at this problem, send me some operation and maintenance orders, I executed, shot to operation and maintenance, operation and maintenance have not found significant problems. After back and forth several times, for the operation and maintenance do not report too much hope
But also to find technical Great God helped me to see the group, the Great God also made a number of command, sent his shots after the execution, to no avail; they view the local 8500 port who occupy different contrast the two machines; went telenet see if the port is on of; even compare the two versions of the machine docker, my local is version 2.0.0.2, he is version 2.0.0.3, I upgraded to 2.0.0.3 .. . .
In this way, one day later, the problem has not yet fundamentally solved
The next day, it really reproduce the problem again in order to ensure the completion of the first day of work, only to restart docker, and then restart the docker container.
This problem must be resolved, otherwise a lot of trouble, because after the restart docker, local 5 projects consul had to rely on reboot again
Must not tear one hundred ride sister, I have been thinking stroke, several colleagues have been installed environment, docker version, image version is the same, and even run the same set of commands are used, the status quo is no problem with them, I was the only one after another a problem that must be my local which is a problem. I am a local and they are local, which certainly is not the same place, in all likelihood, to that pounded ghost
In this way rule out one by one, and finally found a suspicious software - way dictionary
In order to determine this issue, restart the computer, restart, first put the proper way to exit the dictionary, and then start docker, and then start the project, one day later, mapping problems before they occur, and never appeared before.
At this point, the truth come to light, it is the proper way dictionary pot. After work computer, it will not install the
