-
Notifications
You must be signed in to change notification settings - Fork 23
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
Fix Permission denied: '/var/lib/ckan/storage/uploads/group' #41
Comments
I have just tested your "Steps to Reproduce" and I don't get the same behaviour. I don't get an error. What do you mean by a "custom image" I'm building and running the CKAN image from https://github.com/ckan/ckan-docker/tree/master/ckan which by default is using the CKAN base image from https://github.com/ckan/ckan-docker-base/tree/main/ckan-2.10/base |
I have this issue, too, when creating new organisations. FROM ckan/ckan-base:2.10.4 in my Dockerfile to create a custom image, so it's the production image, not the DEV image. Directory structure + permissions:
As you can see, the directory structure has been created by root user, instead of the ckan user. The proposed approach, to change permissions via Edit:
BEFORE creating an organisation. This creates a path When i remove the storage directory manually and run ckan in ckan user context via
Then permissions are fine and organisations can be created. Therefore the bug seems to be within the user add command, do you agree? |
Expected Behavior
After editing the organization and click
create
, the organization is correctly persisted.Current Behavior
After editing the organization, when
create
is clicked, 500 is thrown, and the following log is printed:Possible Solution
The folder
/var/lib/ckan/storage/uploads/group
does not exist when the exception happens. So I tested two things:mkdir /var/lib/ckan/storage/uploads/group
chmod u+rwx /var/lib/ckan
I believe there is some inconsistence with user permissions. The second command seems more reasonable to me, but I am not aware of other possible implications, that is why I oppened this bug.
Steps to Reproduce
create
Context (Environment)
OS:
Darwin 23.2.0 Darwin Kernel Version 23.2.0: Wed Nov 15 21:55:06 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T6020 arm64
Docker:
Docker version 24.0.6, build ed223bc820
Colima:
colima version 0.5.5
Detailed Description
On line 94, the user
ckan
is set as owner of the folder${CKAN_STORAGE_PATH}
. On top of it, we could ensure the owner has rights to read, write and execute files.Possible Implementation
Replace line 93 and 94 from ckan-base Dockerfile by the following command?
The text was updated successfully, but these errors were encountered: