Closed jdhoffa closed 3 years ago
FYI, what I see locally
The steps I follow to run the Dockerfile
are (from within pactaCore):
bin/setup-io
docker-compose up --build
The output folder created by bin/setup-io
(prior to being populated with data) is (prior to running docker
):
The output folder after:
Confusingly, even though I pass the -R
flag, the recursive files don't seem to have the same permissions:
I leave this as a draft, since it seems I haven't solved the problem.
A conversation with @maurolepore seems to suggest that this has been solved? Closing for now.
For the record, right now this is done here: We get the permissions from the input/ directory in the host computer (mounted) and apply them recursively to all files in the output/ directory in the container -- which then gets copied to the host computer.
As the input/ directory in the host computer is created by the user, they have full access; this process ensures they also have full access to the resulting output/ directory.
Here I recursively
chmod 774
the working_dir folder inbin/run-pacta
.This will give the following permissions:
Since
bin/run-pacta
is run inside the docker container, this gives that directory those permissions within the container.One open question I have: I wonder if this approach would be different depending on the mounting type (volume or bind).
Maybe closes #22