Skip to content

Jobs documentation - #26251

Draft
glours wants to merge 2 commits into
docker:mainfrom
glours:jobs-documentation
Draft

glours wants to merge 2 commits into
docker:mainfrom
glours:jobs-documentation

Conversation

@glours

@glours glours commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

Description

Add documentation for the experimental jobs feature: one-shot workloads that
Docker Engine runs on demand or on a cron schedule, declared with a new
top-level jobs element in a Compose file.

  • Compose how-to with a walkthrough (compose/how-tos/jobs.md)
  • Compose file reference for jobs, triggers, and schedule
  • Engine page to turn on the jobs extension and use docker job
    (engine/daemon/jobs.md)
  • summary.yaml entries marked Experimental, with no version number
  • Links from the profiles and init containers pages

The extension is off by default, so every page is marked as experimental.

Related issues or tickets

Reviews

Keep as a draft until the Engine, CLI, and Compose changes ship. The
walkthrough was run against an Engine with the extension turned on.

Needs a reviewer's call: the security warning on the Engine page, and whether
the extension is available on Docker Desktop.

  • Technical review
  • Editorial review
  • Product review

glours and others added 2 commits October 2, 2026 17:39
Document the experimental jobs feature: one-shot workloads that Docker
Engine runs on demand or on a cron schedule, declared with the new
top-level jobs element in a Compose file.

Add a Compose how-to with a walkthrough that was run against an Engine
with the extension turned on, a reference page for the jobs, triggers,
and schedule attributes, and an Engine page for turning on the jobs
extension and using the docker job commands. Add the "Compose jobs" and
"Docker Engine jobs" entries to data/summary.yaml, marked Experimental
with no version number because the feature isn't released.

Signed-off-by: Guillaume Lours <glours@users.noreply.github.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The profiles reference said that no top-level element other than
services is affected by profiles. Jobs honor profiles, so name them as
the exception. The init containers page says that scheduled backups
are the wrong use for init containers, so point to jobs for that case.

Signed-off-by: Guillaume Lours <glours@users.noreply.github.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@netlify

netlify Bot commented Oct 2, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for docsdocker ready!

Name Link
🔨 Latest commit 24a3d72
🔍 Latest deploy log https://app.netlify.com/projects/docsdocker/deploys/6abfd0bcb724b8000887ac4c
😎 Deploy Preview https://deploy-preview-26251--docsdocker.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@github-actions github-actions Bot added area/engine Issue affects Docker engine/daemon area/compose Relates to docker-compose.yml spec or docker-compose binary labels Oct 2, 2026
@glours glours self-assigned this Oct 2, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/compose Relates to docker-compose.yml spec or docker-compose binary area/engine Issue affects Docker engine/daemon

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant