We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Currently, we need to run the Galaxy Docker image with --privilege to get CVMFS integration.
--privilege
If we could reuse a the upstream CVMFS container and bind mount a deployment of this into the Galaxy Docker image we don't need priv mode.
docker pull registry.cern.ch/cvmfs/service:latest docker run --rm -d \ -e CVMFS_CLIENT_PROFILE=single \ -e CVMFS_REPOSITORIES=sft.cern.ch \ --cap-add SYS_ADMIN \ --device /dev/fuse \ --volume /cvmfs:/cvmfs:shared \ --name cvmfs-service registry.cern.ch/cvmfs/service:latest docker run -v /cvmfs:/cvmfs ... quay.io/bgruening/galaxy
Such a setting would also be useful for other use-cases I think.
Thanks to @natefoo for the idea!
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently, we need to run the Galaxy Docker image with
--privilege
to get CVMFS integration.If we could reuse a the upstream CVMFS container and bind mount a deployment of this into the Galaxy Docker image we don't need priv mode.
Such a setting would also be useful for other use-cases I think.
Thanks to @natefoo for the idea!
The text was updated successfully, but these errors were encountered: