The investigation was all done using Mac OS Catalina 10.15.6, Docker desktop CE 2.3.0.4 / Engine 19.03.12. I hope this helps someone and may explain why it seemed to work sometimes or it works after factory reset or after doing a network prune. ![]() I undid all the suggested fixes in this thread including the daemon json bip config and the extra_hosts suggestion from docker-compose and the API was still able to connect. I was then able to connect to my VPN protected API. I removed the offending user-defined bridge using I listed out all my network bridges usingĭocker network inspect docker network ls -q``Īnd found that one of my network bridge's subnet was set to 172.18.0.0/16 Within my container, I was using curl to simulate an API call to an IP address which was behind a corporate VPN.Īfter much tweaking around, I found that my issue was because of a subnet clash with the 172.18.xx.xx IP address. I tried most of the suggestions in this thread and finally realised the root cause of the issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |