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

**URL:** <https://forums.suse.com/t/do-not-start-a-start-once-container-on-creation/12503>\
**Category:** Rancher 1.x\
**Created:** [November 27, 2018, 5:30pm UTC](https://forums.suse.com/t/do-not-start-a-start-once-container-on-creation/12503 "2018-11-27T17:30:25Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![elisiariocouto](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/elisiariocouto/32/3899_2.png) [@elisiariocouto](https://forums.suse.com/u/elisiariocouto)\
**Post date:** [November 27, 2018, 5:30pm UTC](https://forums.suse.com/t/do-not-start-a-start-once-container-on-creation/12503/1 "2018-11-27T17:30:25Z")

</div>

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