SSH bypass host checking for dev Docker environment

If you have a controlled environment where you are recreating SSH target instances, such as Docker containers, and have integration scripts (e.g., Jenkins), you will often run into SSH warnings that will prevent the CI/CD jobs from completing.

If you are sure the target is in a controlled environment – e.g., within a Docker host/network, you can bypass the checks via:

ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no

You could also update the UserKnownHostsFile but it can be tricky. There probably is a better setup than relying on SSH, but as we transition legacy workflow this works for now.

ssh skip host checking

ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no

see here

Rsync over SSH

Another thing I do just infrequently enough to forget the process. Here is a how-to:

troy.jdmz.net/rsync
[ local file: Using-Rsync-and-SSH ]
I’ll post notes later mebbe…