dependabot / dependabot/dependabot-core
Create a single docker image for python?
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 5.8k
- Forks
- 1.5k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 149
Description
Code improvement description
The docker and uv images are essentially the same, with only very minor differences:
https://github.com/dependabot/dependabot-core/blob/f746ee0f46732b48fd535088d6c81e7491888529/python/Dockerfile
https://github.com/dependabot/dependabot-core/blob/f746ee0f46732b48fd535088d6c81e7491888529/uv/Dockerfile
One difference in uv
I understand that this separation allows the ecosystem docker build to evolve independently, but in practice it often results in duplicated changes such as #13321 and missed bug fixes such as in #13630.
Would it make sense to consolidate these into a single build?
For example, the Python ecosystem image could be built first and then used as the base for the uv ecosystem
Contributor guide
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
Start by comparing python/Dockerfile and uv/Dockerfile, especially the uv lines linked in the issue, then review the duplicated changes in #13321 and the missed fix in #13630. Determine whether one consolidated build can support both ecosystems without losing the documented differences; done means the build arrangement and its behavior are clearly validated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- build-system, devops
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100