-
Notifications
You must be signed in to change notification settings - Fork 3
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
DEST_FINAL is not writable #3
Comments
Could you post the actual contents of the compose file? Current example shows no |
@Caledrith did you manage to get down to this? Back then was unable to reproduce it in any way. |
So sorry, I haven't touched it since I got frustrated haha. I'll see if I can check it out today. |
I finally got around to finding a solution, but I'm not happy with it. Inside of common.sh is the validate_config_common() function, and for whatever reason, on the |
I apologize if there is something about docker I don't understand, but I attempted to build a docker compose yml to run this container.
(1000:1000 is my normal user on the vm)
When I locally use the config file (which is contained on my vm) to sync, it works. In the container logs, the container gives me this log essentially over and over
crond: USER abc pid 1184 cmd sync.sh sendmail: can't connect to remote host (127.0.0.1): Connection refused
When I use
sudo docker exec -it --user abc seedbox-fetcher /bin/sh
to get into the container, I get the following error when I run ./sync.sh[sync-34] ERROR DEST_FINAL /path/to/final] is not writable
This seems insane to me as the /path/to/final permissions are
drwxrwxrwt 2 abc abc 4096 Dec 23 08:23 Downloads
(I realize this is insecure, I just have been beating my head against the wall about this forever).When I execute just
echo "$DEST_FINAL is $( [[ -w "$DEST_FINAL" ]] && echo "writable" || echo "not writable" )"
, I get that the folder is writable. Only within the script does it fail, and I've altered the script to export the condition that's giving this error incommon.sh
.Is there something I'm missing?
The text was updated successfully, but these errors were encountered: