-
Notifications
You must be signed in to change notification settings - Fork 249
Minimise root ownership of application files #172
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…figuration files - Until ckan#172 and ckan/ckan-docker-base#80 to ckan-docker
@kowh-ai I'm just testing the README's "Create an extension" section and it's now failing with a permission error. I can get past it with a change to the command like:
This has the benefit of creating the files as the correct UID from outside the container, so these last two paragraphs can be removed from the section:
But maybe that command is getting long to type in? We could consider putting the "create an extension" command into a script in this repo, what do you think? |
I've made these changes in #185 |
This is necessary to run tests on the new CKAN containers (as of ckan/ckan-docker#172) and apparently also to use the `actions/checkout` action (see actions/checkout#956 (comment)).
This is necessary to run tests on the new CKAN containers (as of ckan/ckan-docker#172) and apparently also to use the `actions/checkout` action (see actions/checkout#956 (comment)).
This is necessary to run tests on the new CKAN containers (as of ckan/ckan-docker#172) and apparently also to use the `actions/checkout` action (see actions/checkout#956 (comment)).
Fixes: this issue
To improve the security of CKAN images and containers, it is advised that all files and directories related to the application be assigned to a dedicated non-root user. Moreover, running CKAN processes under a separate non-root user account strengthens system security by minimising the privileges of the running services.
To be applied along with the main ckan-docker-base update: ckan/ckan-docker-base#80