[WIP] Conda docker env for testing #168
Draft
Conversation
This file contains 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
|
cc @rohinb2 |
DenisYay
reviewed
Dec 7, 2023
| @@ -21,6 +32,7 @@ RUN apt-get update --allow-insecure-repositories && \ | |||
| COPY $RUNHOUSE_PATH /app/runhouse | |||
|
|
|||
| # If using a local version of runhouse, install it from the local directory | |||
| RUN conda install grpcio | |||
There was a problem hiding this comment.
I think this can probably go above line 34
* Install python3-pip * SHELL /bin/bash --login -c before RUN activate base * pip install cryptography and pyopenssl
…into conda-docker
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.
trying to use existing miniconda base for docker clusters for testing conda envs. current running into some dependency/version conflicts (colorama, crypto) leading to erroring when restarting runhouse on the cluster.