@@ -13,3 +13,31 @@ It might make good sense to volume-mount the following directories:
-`/etc/cron.weekly/` (can be read-only)
-`/etc/cron.hourly/` (can be read-only)
-`/etc/cron.monthly/` (can be read-only)
## Environment variables
-`SSH_KNOWN_HOSTS` (default: empty)
Known hosts entries to add to `/etc/ssh/ssh_known_hosts` file, in the correct format of `known_hosts` file (described in `sshd` manual).
## `ssh_known_hosts` assembly
If `/etc/ssh/ssh_known_hosts` file does not exist, it will be created. If an `/etc/ssh/ssh_known_hosts.template` exists, it will be used as a template. The file will then be populated with container's own ECDSA public key, and contents of `SSH_KNOWN_HOSTS` environment variable.
## Paths
-`/etc/ssh/ssh_known_hosts.template`
If that file exists, it is used as a template for `/etc/ssh/ssh_known_hosts` within the container.
-`/var/pubkeys`
This is where cron's public key will be placed. Volume-mount it into other containers to be able to use it (you can even use `inotify-watch` to watch it).
-`/etc/cron.d/` (this has to be read-write, for `root`->`cron` user replacements)