SSWConsulting / SSWConsulting/SSW.Website
💸 Docker Secrets
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 14
- Forks
- 10
- Avg merge
- 13h 51m
- Merged PRs (30d)
- 38
Description
Description
While debugging the Docker image locally, Docker Desktop suggested improvements regarding how we pass our secrets to the Dockerfile.
Figure: Recommendations around secrets with Docker Desktop
Proposed solution
We should follow the suggested way by Docker - https://docs.docker.com/engine/swarm/secrets/?utm_source=chatgpt.com
Contributor guide
No contributing guide indexed for this repository
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 by reading the repository's Dockerfile and the linked Docker secrets guidance, then identify how secrets are currently passed during image builds. Done means the Docker configuration follows the recommended secrets approach without exposing secret values in the image or build configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, dockerfile
- Domain
- devops, security
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100