Container workflows offer too little control over names and tags
Developers want to organize container images and identify containers with project-specific names, tags, and repositories. In the signals, AWS CDK sends images to a shared ECR repository, while a devcontainer workflow requires a separate build-and-retag workaround; another developer is looking for a simpler Rust image-building workflow. These requests point to fragmented, tool-specific ways to build and identify containers.
For developers building and managing project containers. Mentioned from Sep 2020 to Jan 2025 on GitHub and Hacker News.
4 different people described this problem in 4 separate discussions.
- Indie fit
- 4.0/10
- Pain
- 5.5/10
- Frequency
- 5.8/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
Every image created for any project using same AWS account/region ends up in very same ECR which makes image management impossible
It would be much easier that I can than upload the image to a Artifactory and not have to re-tag it. Currently it's only possible with this very dirty workaround:
breemts on GitHub (microsoft/vscode-remote-release)Sep 2020+39 upvotesAsked for a toolHas a workaround
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 4 places to find your first customers
- 2 more quotes from people who have this problem
- Current workarounds, existing solutions and risks