Check sandbox readiness before a document task

A working Docker engine is only one dependency. The selected workspace, authentication and document tools must also support the intended task.

Work through these checks

1. Docker

confirm the engine is running. Record the evidence or the unresolved question before moving on.

2. Image

complete sandbox preparation. Record the evidence or the unresolved question before moving on.

3. Files

verify selected resources and the writable workspace. Record the evidence or the unresolved question before moving on.

4. Auth

check the CLI can authenticate inside the sandbox. Record the evidence or the unresolved question before moving on.

5. Output

create and open a small real document. Record the evidence or the unresolved question before moving on.

Put the checklist to work

Ask for a tiny DOCX with a heading and table before submitting a long formatted report.

Keep the checklist beside the task brief and the actual output. Mark a check complete only after inspecting the relevant file, setting or event. If a required check cannot run in the current environment, describe that gap and choose an appropriate next review rather than substituting a confident summary.

A boundary to remember

Do not switch to host execution automatically to hide a sandbox error; choose the environment deliberately.

For the corresponding controls and troubleshooting steps, read the desktop help guide. These checks are a practical review aid; adapt them to the specific source material and intended use of your deliverable.