[Infrastructure] Publish Docker Container on quay.io
Open
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 3
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Conda-forge and bioconda seem to use https://quay.io rather than docker hub, so we should check if it makes sense to host our images on both registries and what the restrictions for the individual registries are.
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. Start by locating how this repository currently builds and publishes its Docker images, then review quay.io and Docker Hub requirements and restrictions. Done means documenting whether both registries are suitable and defining the publishing changes needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100