Closed seanstaley closed 2 years ago
@duffmanpdx and @Paul-Hess This PR looks good to me, but I'm confused about why we didn't need these lines for it to work in our dev/staging/prod clusters. Any ideas?
@duffmanpdx and @Paul-Hess This PR looks good to me, but I'm confused about why we didn't need these lines for it to work in our dev/staging/prod clusters. Any ideas?
first guess would be that our build system that creates the directories that these bind mount to already have the proper permissions for the user we use set as default, we made some changes to users and permissions to stop the hub from running as root that may have made this come up downstream
When trying to start up the latest Docker image, I encountered some permission issues in the logs.
It appears that the user that the user the image utilizes does not have all the permissions that it needs. This PR gives the user that the container chooses to use permissions to own these directories.