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? 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
currently, 2 cvmfs-atlas containers won't share their cache even if they run the same exact command atlas read-gen-event.py.
cvmfs-atlas
atlas read-gen-event.py
one way to fix this is to put a squid container in front of the cvmfs-xyz containers.
cvmfs-xyz
another way is to VOLUME-mount CVMFS_CACHE_BASE=/var/scratch/cvmfs in all cvmfs-xyz images and provide a data-only container exporting that VOLUME.
VOLUME
CVMFS_CACHE_BASE=/var/scratch/cvmfs
AFAICT, all the possible solutions will require a 2-container (or pod-like) setup.
The text was updated successfully, but these errors were encountered:
does this work perhaps? seems like at least for NFS shares specifying the VOLUME with the ':shared' postfix works
moby/moby#4213
can't test right now since hepsw/cvmfs-atlas:latest is hangint while trying to mount :-/
Sorry, something went wrong.
sbinet
No branches or pull requests
currently, 2
cvmfs-atlas
containers won't share their cache even if they run the same exact commandatlas read-gen-event.py
.one way to fix this is to put a squid container in front of the
cvmfs-xyz
containers.another way is to
VOLUME
-mountCVMFS_CACHE_BASE=/var/scratch/cvmfs
in allcvmfs-xyz
images and provide a data-only container exporting thatVOLUME
.AFAICT, all the possible solutions will require a 2-container (or pod-like) setup.
The text was updated successfully, but these errors were encountered: