AIO Notify Push container does not start (Permission denied)

ℹ️ Support
21

I think you’ll have to wait for 7.7.0

22

Sorry for digging up this old thread. Running AIO v9.4.1 it seems I’m facing the same problem:
/start.sh: line 57: /nextcloud/custom_apps/notify_push/bin/aarch64/notify_push: Permission denied

But permissions look okay:

# ls -l /mnt/hdd2/docker/volumes/nextcloud_aio_nextcloud/_data/custom_apps/notify_push/bin/
insgesamt 12
drwxrwxr-x 2 www-data www-data 4096  8. Aug 10:46 aarch64
drwxrwxr-x 2 www-data www-data 4096  8. Aug 10:46 armv7
drwxrwxr-x 2 www-data www-data 4096  8. Aug 10:46 x86_64
# ls -l /mnt/hdd2/docker/volumes/nextcloud_aio_nextcloud/_data/custom_apps/notify_push/bin/aarch64 
-rwxrwxr-x 1 www-data www-data 20644712  8. Aug 10:46 notify_push

Anything I missed?

23

This exact problem was annoying me for a while now.
In my case, I had mounted the drive with my docker volumes as noexec, thus the volumes would be mounted as noexec in the container.
The permissions on the files do not matter in this case.

Check if the directory is mounted as noexec:

mount | grep noexec

and look if /mnt/hdd2/ is listed. If yes, remove the noexec flag from /etc/fstab and remount the drive or reboot the system.

Reference:

24

Thanks for the hint.

Indeed it was, as part of the defaults option in /etc/fstab. I added the option exec to the mount line and now it works. :tada: