aws-samples / aws-samples/lza-validator
[Feature Requests] Publish pre-built docker containers to a public repo
- Dominant language
- Shell
- Stars
- 27
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
As a user I would like to not have to work through the steps to build a docker container for use. One should be readily available. It would also alleviate build issues based on machine as see in PR #8.
Pushing to the public ECR repo seems like a logic choice since this is an AWS project but pushing to DockerHub could work as well. Would effectively make this comment and running in Github less headache if every end user of LZA didn't have to build the same image. https://github.com/aws-samples/lza-validator/issues/7#issuecomment-2167207127
But also makes implementing #7 request easier as well since github actions can just be a layer on top of that docker container. https://docs.github.com/en/actions/creating-actions/creating-a-docker-container-action
Contributor guide
Research direction
Review PR #8 for the reported container build issues and issue #7 for the related GitHub Actions request. Compare publishing to AWS ECR versus DockerHub, then define the container publishing workflow and verify that users can pull a public image instead of building locally.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, docker, github-actions
- Domain
- cloud, devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100