Do not start a 'start-once' container on creation


#1

Hello. I’m using Rancher’s container-crontab to run some cron jobs on my cluster.
I’m setting the container as a ‘Start Once’ service and I’m setting the schedule in the labels. The container is running accordingly to the schedule.
One annoying caveat is that everytime I upgrade the container (a bugfix as an example), the container is started on deploy-time. Is there any way to prevent a ‘start once’ container to start on creation but keeping the crontab to start it on the cron schedule?

Thanks in advance