Rare error after moving laptop from one network to anotherJune 18, 2019 at 7:48pm (Edited 6 months ago)
I recently discovered that a variety of "name resolution" errors are caused by the Gigantum Client having a network configuration from a previous network. If you see name or DNS resolution errors, a restart of the client will resolve this.
As far as I can tell, the Docker daemon is supposed to take care of this, but sometimes it doesn't!
If you're interested in further details or status of a cleaner fix, please chime in here, or on the related GitHub issue https://github.com/gigantum/gigantum-client/issues/860
June 18, 2019 at 8:39pm