You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
but unfortunately the start up script uses the existance of the directory to decide if it needs to create the contents of the directory.
In init-openssh-server-config/run:42, you are checking the existance of /config/sshd/sshd_config not if the sshd folder exists. Here it works and ./ENV/ssh/sshd is filled properly. Similar is true with the logs.
The problem is with ssh_host_keys. On init-openssh-server-config/run:48, it tests if [[ ! -d /config/ssh_host_keys ]];. Docker has created the folder but it is empty. The test fails and the keys are not created. The container starts but sshd is not accepting connections.
Can you change that bit to test for the existance of ssh_host_rsa_key.pub instead. Or if you didn't want to touch the key file, create some .dos-created file flag to test for instead of using the directory?
Reason for change
My ENV folders are just configuration which is kept and tweaked. The mounts folders are connected to cloud storage buckets. They are both treated very differently and having them both together means loads of extra work.
Proposed code change
Can you change that bit to test for the existance of ssh_host_rsa_key.pub instead. Or if you didn't want to touch the key file, create some .dos-created file flag to test for instead of using the directory?
There's probably a couple of options on the table for a solution.
We only support mounting a /config folder and not any of its subfolders or files. We can't (nor we want to) account for any weird thing end users might do just because they feel like it. It's way too much additional work for no gain and is a rabbit hole we'd rather not go down.
Activity
github-actions commentedon Jan 10, 2026
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
aptalca commentedon Jan 10, 2026
We only support mounting a
/configfolder and not any of its subfolders or files. We can't (nor we want to) account for any weird thing end users might do just because they feel like it. It's way too much additional work for no gain and is a rabbit hole we'd rather not go down.