-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
Permission denied for redis:import #248
Comments
Are you running the import/export over ssh? |
@josegonzalez Yes, they are running with the |
Same result running as root on server:
|
Other than that warning - which we should fix - seems fine here:
Can you run the following and post the output?
The dump.rdb in there might be owned by root for some reason and therefore you don't have access to write to it. |
The folder is empty. |
Had the case that there is a file:
Really confusing... 😄
|
I think I've fixed it like this: suppress_output service_container_rm "$SERVICE"
"$DOCKER_BIN" container run --rm -v "$SERVICE_HOST_ROOT/data:/data" "$PLUGIN_IMAGE:$PLUGIN_IMAGE_VERSION" bash -c "rm -f /data/dump.rdb"
+ "$DOCKER_BIN" container run --rm -i -v "$SERVICE_HOST_ROOT/data:/data" "$PLUGIN_IMAGE:$PLUGIN_IMAGE_VERSION" bash -c "cat > /data/dump.rdb" < <(cat)
- cat >"$SERVICE_HOST_ROOT/data/dump.rdb"
"$DOCKER_BIN" container run --rm -v "$SERVICE_HOST_ROOT/data:/data" "$PLUGIN_IMAGE:$PLUGIN_IMAGE_VERSION" bash -c "chown redis: /data/dump.rdb"
suppress_output service_start "$SERVICE" It also makes sense, as we are trying to manipulate a data fs-store outside from the actual used container. |
Wait so was there a file inside the container or outside the container? |
I've never checked inside the container. I just realized that we always interact with the dump file from within temporary or the service container itself, except for the stdin redirect to the file (write operation) is running on the host system. |
Sorry I'm asking where this is from: #248 (comment) You mentioned previously there was nothing at that directory but now there is? Just trying to figure out whats going on since your comments aren't super clear and I'm unable to replicate this otherwise. |
Here the state after every command, just splitted for better overview. Cleanup
Create
Export
Import
|
Description of problem
Running
redis:import
to import previously exported data causes permission error.How reproducible
I've just created the service and exported the data to a file, after that just import it with the commands in streps to reproduce.
Steps to Reproduce
Actual Results
Expected Results
Imports the data without error.
Environment Information
dokku report APP_NAME
outputThe redis service isn't linked to any application yet.
Here is the output of the command with an app:
How (deb/make) and where (AWS, VirtualBox, physical, etc.) was Dokku installed?:
Using the install script (deb) on a physical server.
Additional information
Latest lines of the command with trace:on:
Permissions of the folder:
The data folder is empty.
After changing the permission with
chown dokku:dokku /var/lib/dokku/services/redis/rtest/data
it continues but fails at start of redis; after that the permission will be set back as listed above.Full output
The text was updated successfully, but these errors were encountered: