Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use language package managers instead of os package manager for the dockerfile. #749

Open
seivan opened this issue Feb 21, 2025 · 1 comment

Comments

@seivan
Copy link

seivan commented Feb 21, 2025

Read a list of (lang, version) from either local ./runme.yaml or from $RUNME_CONFIG ( global on host).
Then feed those to the language package managers like rustup, or nvm, ruby-env or alternatives. There's also mise which would let you just iterate over (lang, version) and feed it into a file on the container and let it manage the rest:

[tools]
node = '22' 
python = '3'
ruby = 'latest'

That being said I recommend devbox
because apart from languages, it would also allow for any binary that you could run locally and it works on CI out of the box .

 "packages": [
        "ripgrep@latest",
        "[email protected]"
    ]

instead of this

The benefit of using individual language manager is that it's easier to switch them out.

@seivan seivan changed the title Use language package managers instead upstream languages for the dockerfile. Use language package managers instead of os package manager for the dockerfile. Feb 21, 2025
@sourishkrout
Copy link
Contributor

@seivan could you be more specific what you mean with "for the dockerfile" please? I'm a bit lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants