Currently if the relay server container is rebuilt (which it occasionally needs to be if files are updated) its SSH host keys will change and the VLAB client script will throw WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! errors.
To avoid this (and make rebuilding the relay less of a disruptive process) we could make the host keys for the relay across rebuilds, either by taking them from the server that the container is running on, or generating a set with the VLAB internal keys and mapping them into the container appropriately.
Currently if the relay server container is rebuilt (which it occasionally needs to be if files are updated) its SSH host keys will change and the VLAB client script will throw
WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!errors.To avoid this (and make rebuilding the relay less of a disruptive process) we could make the host keys for the relay across rebuilds, either by taking them from the server that the container is running on, or generating a set with the VLAB internal keys and mapping them into the container appropriately.
See here for some ideas - https://github.com/netresearch/docker-sftp/blob/master/README.md#providing-your-own-ssh-host-key.