containers
containers copied to clipboard
Add conda to PATH variable in `standard` container
Hi there,
I did a little testing with the databricksruntime/standard container, and while I see that conda is installed, I am not able to call it. I had to create a Dockerfile with the following code
FROM databricksruntime/standard:latest
ENV PATH /databricks/conda/bin:$PATH
It seems a little silly to have conda installed but not accessible. Would it be possible to modify the databricksruntime/standard image (and other related images. python
?) to have the ENV PATH /databricks/conda/bin:$PATH
line included?
@mengxr @Loquats does the above make sense? any potential issues?
Just pinging on this issue. Any thoughts?
Seems like the people who might know are busy. Can you try it out and report back? I think the PATH might be dynamically modified during startup.
I have a container where I basically run
FROM databricksruntime/standard:latest
ENV PATH /databricks/conda/bin:$PATH
RUN apt-get update && apt-get install make
and it works fine. Mostly I'm just suggesting making this change upstream so we minimize the amount of change for downstream usage, but I wanted to open this as an issue before doing a PR in case this would cause issues for y'all. But I can open the PR if it helps with things.