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

[QST]: Why is the cuopt release so bad architecturally? #42

Open
deloitte-jcatana opened this issue Feb 16, 2023 · 0 comments
Open

[QST]: Why is the cuopt release so bad architecturally? #42

deloitte-jcatana opened this issue Feb 16, 2023 · 0 comments
Labels
question Further information is requested

Comments

@deloitte-jcatana
Copy link

deloitte-jcatana commented Feb 16, 2023

What is your question?

Why do you use conda environments within a container? You already have the isolation and abstraction of the container, why the need to initialize a separate conda env?
This env is installed to a specific user and UID. If you are not running as the user or UID cuopt doesn't work. It also makes it difficult to layer additional packages on top of the container.

Why not just make it global env for the entire image? Place files in global directories like /usr/local/

@deloitte-jcatana deloitte-jcatana added the question Further information is requested label Feb 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant