Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Rancher crontab scheduling doesn't work. It doesn't pay attention to cron rule and executes restarts container every hour. #8979
Infrastructure Stack versions:
Docker version: (
Operating system and kernel: (
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Rancher HA external DB galera cluster
Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
I have elasticsearch curator container that has ```cron.schedule=0 0 0 * * *" label and ran with started-once, for example. And logs says that this container restarts every hour. And this is the same problem with the other containers.
@aemneina Yep, it's not connected with cron. Rancher just restarts started-once containers.
P.S. Maybe it'll be helpful: the last time, when I saw restart it showed me deadlock in database.
UPD: I think I found the reason of this behaviour and maybe it's not connected with crontab and started-once.
Jul 11, 2017
Tested with Rancher Container Crontab catalog version v0.2.0 on rancher v1.6.3. Logs are added after each container is added with cron.schedule/cron.action or any relevant cron labels. Logs are added when we remove containers with cron labels.