Cron line added didn't remain in crontab on final check. about docker-freepbx HOT 7 CLOSED

Thanks for reporting this. This is a new one and I'm almost thinking it's bad security on FreePBXs part. This makes sense as the image runs under a non priveleged user and /var/spool/cron is restricted to root.

Would you be able to try a few tests for me?

1. chown -R asterisk /var/spool/cron and try a Web Reload
2. chmod -R 777 /var/spool/cron and try a Web Reload?

I am hoping that the first option will fix. Once I hear your response I'll build it into the image ASAP.

from docker-freepbx.

Ran both of them, still getting the same error

from docker-freepbx.

Nuts. Thanks for that. I'm not going to be able to dive deep into this until Wednesday. I did however take a peek at the FreePBX codebase in the meantime and it appears should be intelligent enough to operate in this fashion, in fact has been around for quite a few releases. Hopefully someone else who is running under Kubernetes can add some insight until I'm able to dive into this.

from docker-freepbx.

Looks like it's working if I run it in privileged mode or mount a volume at /var/spool/cron

from docker-freepbx.

Coming back to this, I can add to the routines to manage our own /var/spool/cron if you'd like and have them placed under the exposed volume /data ?

from docker-freepbx.

That would be great.

from docker-freepbx.

Added in Docker Hub tag tiredofit/freepbx:3.6

from docker-freepbx.