Developers struggle to authenticate containerized apps without baking in secrets
Developers and QA engineers need local containers and container builds to access cloud services, but getting host credentials into those workflows can require extra tooling, awkward credential configuration, or passing tokens through environment variables. That can put secrets in source-controlled files or images, or require tools inside containers that are only needed for development. Most signals concern Azure local testing; one also describes AWS CodeArtifact during a container build.
For developers and QA engineers running containerized apps locally. Mentioned from Jul 2019 to Oct 2022 on GitHub.
5 different people described this problem in 3 separate discussions.
- Indie fit
- 6.0/10
- Pain
- 6.7/10
- Frequency
- 6.5/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Businesses
- Competition
- Medium
- Build difficulty
- High
What people said
Quoted word for word. Follow a link to read the whole discussion.
Testing code that uses DefaultAzureCredential in a container locally seems to require a lot of effort, unless one is willing to supply username/password into the environment
The least destructive hack I have come up with is simply to retrieve secrets (e.g. access token) from my host machine (using Azure CLI) and pass it into my docker container using environment variables, and overrule the azure-identity clients, like so:
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 4 places to find your first customers
- 4 more quotes from people who have this problem
- Current workarounds, existing solutions and risks