Docker Standalone's Cron Notes

[davidpiccinini]

Hi!

I'm trying to get a completely working docker setup, but cron inside "php-resque" container is not working.

1. I think that resque.sh inside script folder for repo https://github.com/LiveHelperChat/docker-standalone have some mistakes.

resque.sh have conditionals using (( )) sintaxis and use "<", but will be correct uses [ ] and -lt ?

2. Inside "php-resque" container I see lhc/cron file says:
   @reboot www-data cd /code && ./phpresque.sh >> /dev/null 2>&1
   But I search and not found a process to copy phpresque.sh inside "/code". File "phpresque.sh" is not present by default inside lhc_web's git folder, and no process (in docker deployments instructions) to copy this. Could be "cd /scripts && ./phpresque.sh" ?

3. In other hand, inside that image (php:fpm) I see that cron.d/* files are not running. See same problem in other apps. But if tasks are add to crontab works fine.

[remdex]

All works here :) so that one you will have to figure out

[remdex]

As for initial reboot cronjob it most likely bug, but there is cronjob which runs every minite. So php resque has to start in any case.

Cronjobs has their own dedicate docker instance. They are not running on php-fpm

So in any case there some problems in your setup :)

[davidpiccinini]

When I said php:fpm I refeerer to main original image wich was used for create both images, used in docker-compose file: remdex/livehelperchat-php-resque and remdex/livehelperchat-php-cronjob.

I think there is a problem with cron.d in php:fpm, because if tasks are add to crontab (not by cron.d way) works fine.

I will continue analyzing, any discover I 'll reporte them

[remdex]

Just read instructions in main docker standalone repo. I don't know what you do there :D but instructions tells precisely what steps are needed :)
I have multiple clients using it :)

[davidpiccinini]

Yes, really we analyze this with highest detail, reproduce instructions many times, and create an script for automate these testings, but only detect cron was not running properly, so we resolved as commented below

[davidpiccinini]

The fastest and clean way to resolve without have to rebuild any images or modify nothing was add this to docker compose:

command: bash -c 'echo "$$(cat /etc/cron.d/lhc)" >> /etc/crontab && cron -f'

We adds this line for docker compose's services "php-cronjob" and "php-resque"

Now all works and runs cron jobs as expected!

[remdex]

That's not a correct solution

1. For lhc cronjobs is responsible https://github.com/LiveHelperChat/docker-standalone/blob/master/docker-compose-nodejs.yml#L41 this docker image. Not any other. If you added cronjobs to two docker images that's a major failure because you will running cronjobs twice at the same time....

And if you looked here cronjobs are added during image build
https://github.com/LiveHelperChat/docker-standalone/blob/master/Dockerfiles/cronjob/Dockerfile#L8

2. As for php-resque they have different file https://github.com/LiveHelperChat/docker-standalone/blob/master/Dockerfiles/php-resque/Dockerfile#L8

And from where you took /etc/cron.d/lhc I have no idea as all cronjobs are run using cronjobs files not contrab command...

Is php resque working fine you can check by.

PHP-Resque

docker exec -it docker-standalone-php-resque-1 /bin/bash
ps aux | grep  "resq"

After container has started if you wait few minutes you should see some

root@76e8baff0e48:/var/www/html# ps aux | grep  "resq"
www-data 2449461  0.0  0.0   2576  1536 ?        S    Jan24   0:00 /bin/sh ./phpresque.sh
www-data 2449463  0.0  1.4  94936 29296 ?        S    Jan24   0:23 /usr/local/bin/php resque.php
www-data 2449464  0.0  0.7  94936 15328 ?        S    Jan24   0:44 resque-1.2: Waiting for *
www-data 2449465  0.0  0.7  94936 15328 ?        S    Jan24   0:44 resque-1.2: Waiting for *
root     2472734  0.0  0.0   3324  1536 pts/0    S+   06:19   0:00 grep resq

Basic cronjobs

To check is basic cronjobs is running you can check by

exec -it docker-standalone-php-cronjob-1 /bin/bash
cat /etc/cron.d/lhc

And default lhc cronjobs writes their log to E.g

/data/docker-standalone/livehelperchat/lhc_web/cache

You will always see empty crontab file on both images by default, becase we don't use it!