I have been very happy with this container as a cronjob in the past I recommend it

https://hub.docker.com/r/willfarrell/crontab

On Thu, 21 Jan 2021 at 10:35, Revant Nandgaonkar notifications@github.com wrote:

https://github.com/crazy-max/swarm-cronjob this already does the cron

It runs 1 service to watch for labels and run cron.

If we make it part of yml it'll will work

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/frappe/frappe_docker/issues/405#issuecomment-764541311, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACFC37R3ZZSQSFGFX2GIWTDS277NTANCNFSM4WDCHB7A .

https://github.com/crazy-max/swarm-cronjob this already does the cron

It runs 1 service to watch for labels and run cron.

If we make it part of yml it'll will work

Could we have a long running container which just sleeps and runs the cron every 24 hours?

@revant hi is this still relevent in the latest docker versions? I tried setting the config but it doesn't fix the issue. Do we need to use nginx hostname or something else instead?

<!-- Welcome to the frappe_docker issue tracker! Before creating an issue, please heed the following:

1. Is your issue relevant to the frappe_docker or the main Frappe framework? https://github.com/frappe/frappe . if It's the latter, publish the issue there.
2. Use the search function before creating a new issue. Duplicates will be closed and directed to the original discussion.
3. When making a bug report, make sure you provide all the required information. The easier it is for maintainers to reproduce, the faster it'll be fixed.
4. If you think you know what the reason for the bug is, share it with us. Maybe put in a PR 😉 -->

Description of the issue

Following steps described on the development setup guide, leads to error with crontab. Read crontab frappe: crontabs/frappe/: fopen: Permission denied

Context information (for bug reports)

Operating system: Ubuntu 20.04 Docker version 20.10.2, build 2291f61 bench --version - 5.2.1

Permissions of crontab executable for reference:

frappe@3dc496fd0165:/workspace/development$ ls -l /etc/crontab
-rw-r--r-- 1 root root 1042 Oct 11  2019 /etc/crontab

frappe@3dc496fd0165:/workspace/development/frappe-bench$ ls -l /usr/bin/crontab
-rwxr-sr-x 1 root crontab 43568 Oct 11  2019 /usr/bin/crontab

Steps to reproduce the issue

1. Follow the development setup guide till "setup first bench" stage: https://github.com/frappe/frappe_docker/blob/develop/development/README.md#setup-first-bench
2. Upon setting up first bench you might see this error Read crontab frappe: crontabs/frappe/: fopen: Permission denied

Observed result

Following error occurs when setting up bench: Read crontab frappe: crontabs/frappe/: fopen: Permission denied

Expected result

This error should not occur.

Stacktrace / full error message if available

N/A

re open if needed.

ah ok then. I thought only mine was acting up. Thanks for confirming and for the workaround.

Description of the issue

When edit a py file, browser not get the modification if dont restart Bench Web

Steps to reproduce the issue

1. install docker following this guide
2. enable develop_mode and start Bench Web: This command starts all processes with the exception of Redis (which is already running in separate container) and the web process. The latter can can finally be started from the debugger tab of VSCode by clicking on the "play" button.
3. edit a py file adding, for example, frappe.msgprint("hi")
4. refresh your browser. It doesnt show anything
5. restarting Bench Web
6. browser show the message

Observed result

no message showing in the browser

Expected result

hi message

Stacktrace / full error message if available

no error appear

If you use debugger feature auto reload won't work

https://github.com/frappe/erpnext/wiki/VSCode-Debugging-for-Frappe-Python#caveats

Try installing the crontab or any other packages as needed.

You can even modify permissions of things using sudo.

sudo is available in the bench devcontainer for convenience.

Ideally this should not happen.

It is not happening on windows machine with docker desktop as well.

fixes permission denied error during site creation Error faced in PWD and docker swarm

bench cli sets up a local crontab that does the backups.

In case of docker, there is no crontab that runs in any container. So instead container based solution is recommended as mentioned in previous message.

thanks to Gavin D'Souza and Aditya Hase from frappe team for help

https://github.com/frappe/bench/blob/e16824f23e0afd1d74bf2290a580533239c04064/bench/utils.py#L388-L408

Solution:

• [ ] edit single-bench and multi-bench compose files to accommodate https://github.com/crazy-max/swarm-cronjob
• [ ] move backup cronjob part from wiki to docker swarm setup docs
• [ ] Mention this as part of kubernetes setup docs

I can confirm this issue.

My backups are shown on page because I've a separate CronJob that does the backups every 12 hours.

Workaround: k8s : https://helm.erpnext.com/kubernetes-resources/create-backup-and-push-to-cloud-cronjob docker: https://github.com/frappe/frappe_docker/wiki/Backup-and-Push-to-cloud-Swarm-Cron-job

fixes permission denied error during site creation Error faced in PWD and docker swarm