-
Notifications
You must be signed in to change notification settings - Fork 181
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
Generate a Generic Container? #279
Comments
Wow this is awesome!! In fact, instead of having this for the fallback scenario, it should be the default. cc @Lagoja |
Thanks! The one thing I'd like to improve upon is to figure out a way to have a one liner "install the latest devbox" that will work in the container. If we use something like the above, we'd minimally want to expose the version as an $ devbox build --name ghcr.io/rse-ops/openmpi-devbox in a directory with a devbox.json and magically get a container with it! |
I agree this should be the default behavior. I think having a way to get a generic container that has your packages + configuration installed could help a lot with portability. We'll add this as a task. Thanks for suggesting @vsoch |
Heyo! I'm trying this out on a few computers (looking for issues) - right now on an older ubuntu and hit:
Going to keep debugging but want to keep you in the loop! Update: I couldn't reproduce this on a newer OS (ubuntu 20/22.04) so I think it might just be an old OS issue. I wouldn't worry if it was just for my old laptop this happened! |
@vsoch this is done with the newest update 0.2.0. Use |
hey devbox! I was wondering - why not have a fallback container generation for "all other cases" that are outside python, go, etc? For example, if we use nixos/nix and then the best way to install devbox, and then initiative a shell with a command that exits (to install stuffs) it would be fairly straight forward to have that be the fallback - here is an example: https://github.com/rse-ops/devbox/blob/main/bases/devbox/Dockerfile. And maybe I'd even do:
So the default entrypoint is devbox shell right into the environment (not I haven't tried this, my container build above I default to a shell and then run
devbox shell
at my leisure!The text was updated successfully, but these errors were encountered: