Search found 6 matches
- 31 Jan 2024, 19:30
- Forum: Scripting and Automation
- Topic: Force relative symlinks in a docker context where absolute symlinks don't work due to different file system views
- Replies: 8
- Views: 10915
Re: Force relative symlinks in a docker context where absolute symlinks don't work due to different file system views
Ok i change docker image and use you re now, it s seems to be better i just need to adjust some settings
- 27 Jan 2024, 18:37
- Forum: Scripting and Automation
- Topic: Force relative symlinks in a docker context where absolute symlinks don't work due to different file system views
- Replies: 8
- Views: 10915
Re: Force relative symlinks in a docker context where absolute symlinks don't work due to different file system views
I use Rutorrent
In filebot container storage folder are in the root so real path is /storage
my docker compose for filebot
version: '3'
services:
filebot:
container_name: filebot
image: jlesage/filebot
restart: unless-stopped
volumes:
- /home/SeedboxData:/storage:rw
- /home/SeedboxConf ...
In filebot container storage folder are in the root so real path is /storage
my docker compose for filebot
version: '3'
services:
filebot:
container_name: filebot
image: jlesage/filebot
restart: unless-stopped
volumes:
- /home/SeedboxData:/storage:rw
- /home/SeedboxConf ...
- 27 Jan 2024, 15:47
- Forum: Scripting and Automation
- Topic: Force relative symlinks in a docker context where absolute symlinks don't work due to different file system views
- Replies: 8
- Views: 10915
Re: Force relative symlinks in a docker context where absolute symlinks don't work due to different file system views
Ok thanks for quick anwser, i just want it s running well 
so what i need to change exactly , my script or my docker volume ?
so what i need to change exactly , my script or my docker volume ?
- 27 Jan 2024, 15:05
- Forum: Scripting and Automation
- Topic: Force relative symlinks in a docker context where absolute symlinks don't work due to different file system views
- Replies: 8
- Views: 10915
Force relative symlinks in a docker context where absolute symlinks don't work due to different file system views
Hi i use since 2-3 years this script
docker exec filebot /opt/filebot/filebot -script fn:amc --action symlink -non-strict "/storage/torrents/" --conflict auto -non-strict --log-file amc.log --def movieFormat="/storage/Media/Movies/{fn}-{y}" --def seriesFormat="/storage/Media/TV Shows/{n}/Season ...
docker exec filebot /opt/filebot/filebot -script fn:amc --action symlink -non-strict "/storage/torrents/" --conflict auto -non-strict --log-file amc.log --def movieFormat="/storage/Media/Movies/{fn}-{y}" --def seriesFormat="/storage/Media/TV Shows/{n}/Season ...
- 27 May 2021, 17:52
- Forum: Ubuntu & Desktop Linux
- Topic: The --output option is required
- Replies: 16
- Views: 28942
Re: The --output option is required
Thanks so much it s ok now
- 26 May 2021, 18:43
- Forum: Ubuntu & Desktop Linux
- Topic: The --output option is required
- Replies: 16
- Views: 28942
Re: The --output option is required
hi can you help to modify my script i have same suddently error message all was good during many month
my script :
docker exec filebot /opt/filebot/filebot -script fn:amc --action symlink -non-strict "/storage/torrents/" --conflict auto -non-strict --log-file amc.log --def movieFormat="/storage ...
my script :
docker exec filebot /opt/filebot/filebot -script fn:amc --action symlink -non-strict "/storage/torrents/" --conflict auto -non-strict --log-file amc.log --def movieFormat="/storage ...