laur89/docker-seedbox-rclone-fetch-extract

Dockerised service pulling data from remote seedbox & extracting archives

docker-seedbox-rclone-fetch-extract's Issues

DEST_FINAL is not writable

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.

version: "2.1"
  services:
    seedbox-fetcher:
      container_name: seedbox-fetcher
      image: layr/seedbox-rclone-fetch-extract
      environment:
       - REMOTE=seedbox
       - SRC_DIR=/torrents/rtorrent
       - DEST_INITIAL=/path/to/initial
       - DEST_FINAL=/path/to/final
       - PUID=1000 
       - PGID=1000
    volumes:
     - /media:/data 
     - /path/to/config:/config 

(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 in common.sh.

Is there something I'm missing?