docker-ripper icon indicating copy to clipboard operation
docker-ripper copied to clipboard

Fixes permission error when running on a filesystem with noexec set

Open mellowdrifter opened this issue 1 year ago • 0 comments

If ripper is created on a filesystem with noexec set, then a permission denied happens when trying to run any .sh file directly:

Ripper  | /etc/my_init.d/ripper.sh: line 45: /config/ripper.sh: Permission denied

Logging into the container I see the same:

root@bf76650b6ac1:/config# ./ripper.sh
bash: ./ripper.sh: Permission denied

There is a simple fix though, by calling bash directly on the script it works fine, as it's no longer 'executing' the file directly on the noexec filesystem

root@bf76650b6ac1:/config#  bash /config/ripper.sh
28.09.2024 21:21:33 : Starting Ripper. Optical Discs will be detected and ripped within 60 seconds.

This change works for both exec and noexec filesystems

mellowdrifter avatar Sep 28 '24 21:09 mellowdrifter