-
Notifications
You must be signed in to change notification settings - Fork 20
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
Running in a container #46
Comments
Not sure exactly how you are using this. But there is also a micromamba container here that might be better for your use case? |
@wolfv I need to run the job in the specific container used in this workflow That is a CML container and the point of the job (not the one in that example repository but when I use it in practice) is to re-run an ML pipeline and log all the relevant metrics (which is more or less what CML is for). In the job I need to set up a virtual environment. I can do it "manually" with a bash script, but the environment is relatively big and takes some 4 minutes to set up. I want to reduce the time to some 20 seconds which I can with provision-with-micromamba and caching when not run in the container. So basically, my main usecase is caching the virtual environment but now that I think about it again I guess I'd need to cache the container as well (though maybe not, I am not sure how exactly the caching is done), or create an image which includes the virtual environment already, so I am not quite sure I can actually use provision-with-micromamba here... |
I am trying use your action in a container, specifically this one by Iterative in order to create a workflow with CML.
Unfortunately, I am running into a problem with
.bashrc
(or rather with the user name if I understand the issue correctly)The issue is replicated in this repository.
There is a workflow which should set up an environment with micromamba on a pull request.
There are two branches (apart from main), the workflow works as intended in the one where the CML container is not used and it fails on the following error in the one where the container is used.
It is possible this is not an issue with provision-with-micromamba and that I am doing something wrong (i.e. I don't understand how to set up up correctly when using the container).
Thanks for the help!
The text was updated successfully, but these errors were encountered: