docker: remove dev dependencies from release images #13095
+36
−11
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
docker
settings_changes
valentijnscholten
force-pushed
the
split-dev-dependencies
branch
from
3b1d608 to
ada16f5
Compare
github-actions
bot
removed
settings_changes
valentijnscholten
requested review from
Maffooch and
mtesauro
as code owners
|
Did you consider doing the same for for the Debian dockerfile? |
Yes, it's part of the PR or did I miss a part? |
Maffooch
approved these changes
Sep 3, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I wasn't going to spend time on this, but then Cursor AI got it right almost on the first go.
Some dependencies are only needed for development, we shouldn't install those in the release ("production") images.