Mostly running this PR as WIP because my local dev box is giving me trouble, and I want to run against CI a bit to see if the problem is more general.

It seems that in CI, the Jobs test takes too long to complete 20 iterations. I've cut down the total to 7, which is less than the minimum completion I saw, which was 8.

@derny this needs a rebase now

@thaJeztah Yes, it does, but in any case, the development on Jobs has happened all in a feature branch in Swarmkit, and that feature branch has not quite yet been merged into swarmkit master.

No longer WIP.

Swarmkit will only schedule the number of Tasks needed to reach TotalCompletions, so there won't be any Tasks still running when TotalCompletions is reached. MaxConcurrent establishes the upper bound on how many are scheduled.

Would love to blog around this. Which Docker release is it coming with? Beta bits?

CLI PR is open, pending the merge of this PR.

Amazing. Thank you for the work! When is this planned to be released?

👏 👏 💯

Very nice, thanks for this! I'll soon be able to archive swarm-cronjob 😅

@dperny Thanks for this new feature 👏
@crazy-max When reading the documentation, it seems different from your (crazy 😄 ) swarm-cronjob project: here there is a limited number of executions (TotalCompletions) and no cron equivalent functionality, so please don't archive it. It's still very useful ❤️

@dperny you're a blessing to open source. thank you.

This is really good stuff!

Question: Would it be possible to specify jobs via compose/stack file too? or this will only work via CLI?

Edit: Moving the question to docker/cli#2262 which is where it was being discussed.

Nice work! I would have loved this three years ago 😄 I've actually seen a rise in interest in alexellis/jaas so I think this will be well received by the community of users still on Swarm.

Is it possible to create cron job with swarm?

Answering the last question: evidently not. Swarm jobs are meant to run once and will not be run again if completed:

Jobs are never restarted on reaching the Complete state. This means that for jobs, setting --restart-condition to any is the same as setting it to on-failure.

Source: https://docs.docker.com/reference/cli/docker/service/create/#running-as-a-job

I may have written up some example somewhere, but I think you can somewhat mimic it with a restart policy and delay;

docker service create \
  --name cronish \
  --replicas 1 \
  --restart-condition any \
  --restart-delay 1h \
  alpine sh -c 'do-the-thing'

Yeah, read something like this on Reddit but this doesn't make use of the job feature at all.

(Also --restart-condition already defaults to any so that can be omitted.)

Yeah, read something like this on Reddit but this doesn't make use of the job feature at all.

True, jobs support in Swarm is limited by design. https://github.com/crazy-max/swarm-cronjob does what you are looking for.