Container using system packages
See original GitHub issueWhen running a sorter using run_sorter_container
some system volumens are mounted. On ubuntu and using singularity this can lead to the system installation of spikeinterface (e.g. in ~.local/pythonX.X/site-packages
) to shadow the spikeinterface version installed in the container.
This can lead to confusing version conflicts, but can also be used to provide the container with a specific spikeinterface version. Is this an intended feature or a bug? In the first case it might be good to add a warning if the container internal spikeinterface version is shadowed by the system version.
Issue Analytics
- State:
- Created a year ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Using system packages tutorial | Cloud Run Documentation
It uses Graphviz and is installed as a system package in the service's container environment. Graphviz is used via command-line utilities to serve...
Read more >Installing system packages in Docker with minimal bloat
Learn how to minimize your Docker image size while installing or updating system packages on on Debian, Ubuntu, and RHEL.
Read more >What is a Container? - Docker
A container is a unit of software that packages code and its dependencies so the application runs quickly and reliably across computing environments....
Read more >How to add packages to a container? | Research Computing
The Python package will be installed in your home directory under .local/lib/pythonX.Y where X.Y is the Python version in the container. If the ......
Read more >How to install packages in a Docker container - Edureka
If you want to install packages in the Container, use the RUN statement followed by exact download command . $ RUN pip install...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I believe we don’t have spikeinterface installed in any docker image, so it should always try to install, no?
What happens is that one of the system volumes that is binded in singularity mode is the host’s
$HOME
folder, so one of the paths that Python searches for (and installs) packages is/home/<user>/.local/pythonX.X/site-packages
, so when running in singularity mode it turns out that Python inside container also shares this folder with the host. Which I believe is not desired and also doesn’t happen in docker modeHi Yu Min, I am OK with the patch you did. What I do not understand in that case of Julia is why we try to install spikeinterface package in the container when it is already installed. This should not happen. Am I missing something ?