Workaround problems with interactions when running Taverna Server inside Docker inside a VM. The networking configuration in that situation is non-trivial, and beyond what it is practical to auto-detect. This means that at least it is possible to fix the problem by just adjusting a properties file, instead of having to edit the bean configuration file directly.