SaaShup / SaaShup/netbox-docker-agent
:sparkles: Add support for Docker secrets
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43
- Forks
- 2
- Avg merge
- 40m
- Merged PRs (30d)
- 2
Description
Context
I have a Docker container that expects a file in /run/secrets/admin_password (it is hard-coded).
In Docker Compose, this is done using:
secrets:
admin_password:
file: ./myadminpwd.txt
services:
myservice:
image: ...
secrets:
- admin_password
Though, docker run does not support secrets, as it is a feature only available with Docker Swarm. I wonder how Docker Compose implements it (do they simply bind-mount the file or do they initialize a Swarm?).
Does it make sense to have the Netbox Docker Agent initialize a Swarm on the host it runs on?
Feature Request
I would need a way to specify, when creating a container, a secret either from:
- a file on the host
- a base64 encoded string
If you consider that I should just "bind mount a file" and handle securing that file myself, feel free to close this feature request.
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
The issue names no files, tests, or entry points. First clarify whether secrets should be implemented through Docker Swarm or another mechanism, and define the security expectations for host files and base64 values. Done means container creation accepts both requested secret sources and makes the secret available at the required path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, javascript
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100