Add optional SSH host key persistence #84
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adds a new boolean option, `persist_ssh_host_keys`, to allow users to persist SSH host keys in the /data directory and that secure permissions are set.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add option to persist SSH host keys across container updates
Problem: Container updates cause "REMOTE HOST IDENTIFICATION HAS CHANGED" errors.
Solution: New optional setting
persist_ssh_host_keys(defaults tofalse).When enabled, SSH host keys are stored in persistent storage instead of being regenerated on each container start. This eliminates connection errors due to
known_hostsfile after add-on updates.Usage:
Maintains backward compatibility - existing installations continue working unchanged.
(also updated link on config.yaml
master->main)