All ideasMore in Work

Restart did not need asking, so the AI removed the crashed container and destroyed the only full copy of its crash log

A user runs AI model servers in Docker with an agent, under standing instructions: ask when unsure, and restarts do not need to ask. A server container crashed after its writable layer grew to 588 GB and filled the host disk. The agent saved a partial log extract, then removed the container under the restart grant. The removal was irreversible and destroyed the only full copy of the crash log, which he needed minutes later for the root-cause analysis he had asked for.

This one went wrong. Read what happened so you don’t hit the same problem.

How it works

  1. Standing grant: restarts do not need to ask
  2. A server container crashes, its layer grows to 588 GB and fills the disk
  3. The agent saves a partial log extract
  4. Removes the container under the restart grant
  5. The only full crash log is destroyed
  6. He asks for the root-cause analysis minutes later

Why it’s worth knowing

Restart and remove are one word apart in a runbook and a world apart in what they destroy.

Where it’s from

Summarized from a public post on github.com. See the original ↗

Upgraded prompt

A ready-to-use prompt for this idea, built from research on what makes AI agents do the job right: who the AI should be, the exact steps, and a check to make sure it was done the way you wanted.

1Who the AI should be
2The prompt, with the steps
3The check when it’s done
Upgraded prompts are coming soon.

Try next

Every idea is a real post from someone who tried it, summarized in our words, with a link to the original. App names are swapped for plain words.