search

scipy-conference / procbuild

SciPy proceedings builder
Other
2 stars 10 forks source link

[#39] Fix Ubuntu version, Debian front-end, venv dependency, and UID/… #40

Closed cbcunc closed 5 years ago

cbcunc commented 5 years ago

…GID.

stefanv commented 5 years ago

I don't understand the need for the UID/GID changes (did the caching mechanism change?), but all the rest looks fine to me.

cbcunc commented 5 years ago

@stefanv The dockerfile creates a procbuild user. That user creates the PDFs in a procbuild/cache directory it owns in the container. It is desirable to keep those PDFs on the filesystem of the host by means of a volume mount in a docker-compose.yml file (or by means of a -v option to docker run). That volume will need to be readable/writable by a user on the host. Left to its own devices, the Dockerfile will create a procbuild user with the first available UID/GID, which may or may not match a UID/GID on the host. By providing a UID/GID in the Dockerfile, we can cause it to match some user we have created for the purpose of persisting the cache directory on the host. This is a common enough thing for Dockerfiles to do. I have a docker-compose.yml file I use to run procbuild and front-end it with an nginx container. I may possibly add the docker-compose.yml I use to this repo at a later date.

stefanv commented 5 years ago

Makes sense; thanks for explaining!