While trying to deploy the NMDC EDGE web app as a Docker container running on a VM hosted on Jetstream2, and configuring that web app to access directories created by a Magic Castle cluster, we ran into an issue where the web app could not access those directories.
Hypothesis
It may be the case that the access issues stem from the UID/GID of the user as which the web app runs within the Docker container, not being among those that have access to that directory based upon its ownership and mode (i.e. chmod value). It may be the case that if the UID/GID of the user within the Docker container match that of the owner of the directory, the web app will be able to access the directory.
Task
The task here is to allow the person deploying the web app to customize the UID/GID of the user within the Docker container.
Background
While trying to deploy the NMDC EDGE web app as a Docker container running on a VM hosted on Jetstream2, and configuring that web app to access directories created by a Magic Castle cluster, we ran into an issue where the web app could not access those directories.
Hypothesis
It may be the case that the access issues stem from the UID/GID of the user as which the web app runs within the Docker container, not being among those that have access to that directory based upon its ownership and mode (i.e. chmod value). It may be the case that if the UID/GID of the user within the Docker container match that of the owner of the directory, the web app will be able to access the directory.
Task
The task here is to allow the person deploying the web app to customize the UID/GID of the user within the Docker container.
References: