Remove VOLUME directive in cvmfs-base #8
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Exposing /cvmfs as a VOLUME in the base image seems to prevent
Dockerfiles of deriviative images from making persistent changes to this
directory. In particular, in cvmfs-atlas one gets an error at runtime
because the /cvmfs/atlas.cern.ch directory is missing, despite the fact
that it is created by the Dockerfile at build-time.
Note that end-users can easily expose /cvmfs as a volume at invocation-time with the -v flag, or by using docker-compose.