A Docker entrypoint wrapper which sets up SSH config files based on the following environment variables:
SSH_CONFIG- contents of an SSH config fileSSH_KNOWN_HOSTS- contents of an SSH known_hosts fileSSH_PRIVATE_RSA_KEY- contents of an SSH private RSA keySSH_PRIVATE_DSA_KEY- contents of an SSH private DSA keySSH_DEBUG- enables SSH debug logging
You can also provide base64 encoded versions by adding _B64 to the end of the environment variable (e.g. SSH_PRIVATE_RSA_KEY_B64, useful for environments that don't support newlines) and _PATH for specifying a file to get the contents from (e.g. SSH_PRIVATE_RSA_KEY_PATH, useful for secret stores mounted as volumes).
Things to keep in mind:
- Any existing files in
~/.sshwill be overwritten with these new values - After writing the values to disk the environment variables are unset to help prevent accidental printing
After adding it to the Dockerfile:
#...
# You should use a commit hash rather than "master" in your own version of the below
RUN curl -fL "https://raw.githubusercontent.com/buildkite/docker-ssh-env-config/master/ssh-env-config.sh" -o /usr/local/bin/ssh-env-config.sh \
&& chmod +x /usr/local/bin/ssh-env-config.sh \
ENTRYPOINT ["ssh-env-config.sh","some-command"]You can then configure SSH via environment variables:
docker run -e SSH_KNOWN_HOSTS="$(< ~/.ssh/known_hosts)" ...Or you can pass in the base64 encoded version by appending _B64:
docker run -e SSH_KNOWN_HOSTS_B64="$(base64 < ~/.ssh/known_hosts)" ...Or you can pass a path to a file with the contents by appending _PATH:
docker run -e SSH_KNOWN_HOSTS_PATH="/mnt/secrets/known-hosts" ..../tests.sh || echo "Boo, tests failed."