I am running Rancher 1.6.15, my hosts are on RancherOS 1.2, running Docker 17.09.1-ce.
I have Container-Crontab running from out of the catalog, and in general it seems to fire off my containers when it should. However, in between this (for example I have one that should run once a month), I get a heap of these:
Date Level Event Description
04:09:21 PM INFO service.trigger.info Service already reconciled
04:09:21 PM INFO service.trigger Re-evaluating state
04:09:21 PM INFO service.trigger.info Requested: 1, Created: 1, Unhealthy: 0, Bad: 0, Incomplete: 0
04:09:21 PM INFO service.update.info Service reconciled: Requested: 1, Created: 1, Unhealthy: 0, Bad: 0, Incomplete: 0
04:09:18 PM INFO service.trigger Re-evaluating state
04:09:18 PM INFO service.trigger.info Requested: 1, Created: 1, Unhealthy: 0, Bad: 0, Incomplete: 1
04:09:18 PM INFO service.update.info Requested: 1, Created: 1, Unhealthy: 0, Bad: 0, Incomplete: 1
04:09:18 PM INFO service.update.wait (3 sec) Waiting for instances to start
04:09:18 PM INFO service.update (3 sec) Updating service
04:09:18 PM INFO service.instance.create Creating extra service instance
My cron jobs are designed to be run once a month, and running them multiple times is bad. I have two hosts in this environmental. They have great uptime and resources.
Command for crontab container is : container-crontab (i.e. I have tried ranchermode and non-ranchermode)
Cron is running container v0.5
My client containers are set to Auto Restart Never (start once).
I have the appropriate label (cron.schedule) set on the container, from: @monthly to 0 0 1 * * nothing seems to help. Yet it ran today at 4:09pm
My clients have a command such as: “sh export-monthly_cron_job.sh”
Any idea what I am doing wrong please?