Add swarm key variables to container daemon #6554
Merged
Conversation
This file contains 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
License: MIT Signed-off-by: Caian Benedicto <[email protected]>
License: MIT Signed-off-by: Caian Benedicto <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Modify the container daemon to allow an external swarm key to be assigned to
/data/ipfs/swarm.keyduring container initialization. The environment variables are:IPFS_SWARM_KEYIPFS_SWARM_KEY_FILEThe
IPFS_SWARM_KEYcreatesswarm.keywith the content of the variable itself, whilstIPFS_SWARM_KEY_FILEcopies the key from a path referred by the variable. This enables, for instance, docker secrets support.The
IPFS_SWARM_KEY_FILEoverwrites the key generated byIPFS_SWARM_KEY.The key generated by both variables has permission 0400 (u+r, go-rwx)
License: MIT
Signed-off-by: Caian Benedicto [email protected]