thanks for this useful article. i actually ran into this on my host where docker was running as well, suddenly thinlinc agent thought that one of the virtual docker interfaces was the primary one.
may I add, that i had to restart the vsmagent systemd service after changing the agent_hostname setting for it to take effect:
$ sudo su -
# tl-config /vsmagent/agent_hostname=10.10.0.100
# systemctl restart vsmagent.service
where 10.10.0.100 was the ip of the agent host.