About lossing salt minion key
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 15.7k
- Forks
- 5.6k
- Avg merge
- 2d 44m
- Merged PRs (30d)
- 80
Description
If I deploy salt on docker, all files will be lost after the docker container is restarted, such as the salt minion key file. I manually use the same file '/etc/salt/master' to restart salt, but I can't get the previously authorized salt minion, and salt minion will not automatically re authenticate. How can I make salt minion re authenticate and connect?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Docker deployment details and the /etc/salt/master path mentioned in the issue. Investigate how the minion key is persisted across container restarts and how authorization is restored when it is lost. Done means a documented or verified way for the minion to re-authenticate and reconnect after restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- authentication, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100