Skip to content

offload: product updates#24487

Open
craig-osterhout wants to merge 1 commit intodocker:mainfrom
craig-osterhout:engdocs-3216
Open

offload: product updates#24487
craig-osterhout wants to merge 1 commit intodocker:mainfrom
craig-osterhout:engdocs-3216

Conversation

@craig-osterhout
Copy link
Copy Markdown
Contributor

@craig-osterhout craig-osterhout commented Mar 23, 2026

Description

Updates for upcoming Offload release.

Preview:

Related issues or tickets

ENGDOCS-3216
DCL-1433
#24089

Reviews

  • Technical review
  • Editorial review
  • Product review

@netlify
Copy link
Copy Markdown

netlify bot commented Mar 23, 2026

Deploy Preview for docsdocker ready!

Name Link
🔨 Latest commit 7378791
🔍 Latest deploy log https://app.netlify.com/projects/docsdocker/deploys/69cc3b081f1c49000830db12
😎 Deploy Preview https://deploy-preview-24487--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/desktop Issue affects a desktop edition of Docker. E.g docker for mac area/admin Relates to Docker Admin hugo Updates related to hugo area/offload labels Mar 23, 2026
Copy link
Copy Markdown
Contributor

@docker-agent docker-agent bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assessment: 🟢 APPROVE

Reviewed 11 files with 593 lines of changes. The documentation updates for Docker Offload are well-structured and follow the style guide. No critical issues found in the changed code.

Note: The drafter initially flagged 3 issues, but verification confirmed these were in existing code (not changed by this PR), so they are not reported here per the review guidelines.

Copy link
Copy Markdown
Contributor

@docker-agent docker-agent bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assessment: 🟢 APPROVE

This PR successfully transitions Docker Offload from Early Access to GA with appropriate documentation updates. The changes streamline content and improve information architecture by moving conceptual information to the About page and keeping configuration pages focused on procedures.

Summary:

  • 4 minor issues found (formatting, consistency, clarity)
  • No critical bugs or security issues
  • Changes align with documentation best practices for GA release

@craig-osterhout craig-osterhout requested a review from a team March 26, 2026 22:37
@craig-osterhout craig-osterhout added the status/review Pull requests that are ready for review label Mar 26, 2026
Copy link
Copy Markdown
Contributor

@aevesdocker aevesdocker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All LGTM!

@mslaveck1
Copy link
Copy Markdown

Docker Offload quickstart page:
Prerequisites

  1. A Docker Business seat is required to access Offload. We should make that clear here so users who are on a Team plan don't get confused.

About Docker Offload page:
Key features

  1. "Hybrid workflows: Seamlessly transition between local and remote execution using Docker Desktop or CLI." This may be a little leading for where the product is today. Offload doesn't let you move workloads between local and remote. You can choose to work in a local environment or work in a remote environment but you can't move work between them.

Session management and idle state

  1. "To ensure fair access to cloud resources for all users, Docker Offload implements session management with idle state policies." Offload doesn't have idle policies to ensure fair access to resources, it's to avoid unnecessary costs to Docker. Let's just remove that first clause and say 'Docker Offload implements session management and idle state policies to ensure fair use across all users.' Little bit more generic because we do have fair use policies in contracts.
  2. "2. You receive periodic prompts (every 3 hours)" Can we make this 'every 1 to 3 hours'? If users go above the soft cap time limit then we prompt hourly instead of every 3 hours. Open to alternative ways of conveying this message if you think it makes more sense to put this information somewhere else in these docs.
  3. "3. When the prompt appears, your state becomes idle (lasting up to 5 minutes)." When the prompt appears, the user has 5 min to react to the prompt before the idle timeout timer begins (like a 5 min grace period), your state does not become idle immediately. And during the 5 min idle timeout countdown, the session is not terminated (the user can still work). Users can keep working during the 5 min idle timeout countdown too if they want to but it's not recommended).
  4. "In the idle state, the remote connection is suspended and containers stop running." The session is suspended after the 5 min idle timeout expires.
  5. "In the idle state, you can choose to:" These are actions you take from the prompt not in the idle state.
  6. "Do nothing or select Cancel in the prompt. Docker Offload remains in the idle state." Doing nothing, canceling, or killing the prompt will proceed with the 5 min grace period and 5 min idle timeout countdown.
  7. "Select Resume in the prompt within 5 minutes. Your session becomes active again with all containers, images, and volumes preserved. Return to step 2." Session just continues, there is no becoming active again. Also, Return to step 2 is odd here because the user will keep working not need to worry about the nudge immediately.
  8. "4. If the idle period exceeds 5 minutes, the session ends and any containers, images, or volumes are deleted. Return to step 1 for a new clean session." The idle period exceeding 5 min is related to the soft nudge mentioned in no. 3 as well if idle time is detected at anytime during the session. Not sure if this numbered item is mean to denote general session management policies or specifically following no. 3. I'd also remove Return to step 1 because these are more about how policies work not how the user works. Could say something like a new session can be started normally.
  9. "5. After 8 hours from the start of your session, you will receive a prompt in the Docker Desktop Dashboard to extend your session. At this time, you can extend your session. If you do not extend your session, it ends and any containers, images, or volumes are deleted." Does not have to be consecutive 8 hrs, can be 8hrs over multiple sessions and this will still get flagged. Basically at this 8 hr mark, the soft nudges from no. 3 become hourly instead of every 3 hours.

Configure Docker Offload page:

  1. Because we switched from consumption-based to seat-based there aren't really any settings to configure or manage. I think this page should be called Enabling Docker Offload instead because that's really the only thing Owners do and can we rework this page to just be about managing Offload enablement?

Docker Offload usage and billing page:

  1. Page is called usage and billing but it talks about billing then usage, update title to reflect order of content on the page.

Manage billing

  1. "For Docker Offload, you can view and configure billing on the Docker Offload page in Docker Home Billing. On this page, you can:" link takes you to the Subscription page, that doesn't sound like configure billing, track usage, or manage payment methods

Monitor your usage

  1. "The Offload activity page in Docker Home provides visibility into how you are using cloud resources to run containers." This is less about how you are using cloud resources and more about active users and session time.
  2. "Sign in to Docker Home.
    Select the account for which you want to monitor usage."
    Link takes me to a page where I see all the Docker products, not sure what it means by select the account for which you want to monitor usage... and when I click Offload, I automatically go to the Offload activity dashboard. Maybe it's just my view but want to make sure this is accurate in the steps.

Signed-off-by: Craig Osterhout <craig.osterhout@docker.com>

wording udpate

Signed-off-by: Craig Osterhout <craig.osterhout@docker.com>

agent feedback

Signed-off-by: Craig Osterhout <craig.osterhout@docker.com>

add timing

Signed-off-by: Craig Osterhout <craig.osterhout@docker.com>

vale check

Signed-off-by: Craig Osterhout <craig.osterhout@docker.com>

ui update

Signed-off-by: Craig Osterhout <craig.osterhout@docker.com>

wording update

Signed-off-by: Craig Osterhout <craig.osterhout@docker.com>

update required version

Signed-off-by: Craig Osterhout <craig.osterhout@docker.com>

vale fixes

Signed-off-by: Craig Osterhout <craig.osterhout@docker.com>

feedback

Signed-off-by: Craig Osterhout <craig.osterhout@docker.com>

summary bar

Signed-off-by: Craig Osterhout <craig.osterhout@docker.com>

billing

Signed-off-by: Craig Osterhout <craig.osterhout@docker.com>
@craig-osterhout
Copy link
Copy Markdown
Contributor Author

Thanks @mslaveck1. All the feedback has been applied. For billing, I removed that section as it was a remnant of when the offload billing was more complex than a simple subscription. Our generic admin billing section should cover it now. ptal

Copy link
Copy Markdown
Contributor

@dvdksn dvdksn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

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

Labels

area/admin Relates to Docker Admin area/desktop Issue affects a desktop edition of Docker. E.g docker for mac area/offload hugo Updates related to hugo status/review Pull requests that are ready for review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants