restart_policy.max_attempts is hard to understand.

[alexanderkjeldaas]

File: compose/compose-file/index.md

The documentation for
restart_policy.max_attempts is hard to understand.

max_attempts: How many times to attempt to restart a container before giving up (default: never give up). If the restart does not succeed within the configured window, this attempt doesn’t count toward the configured max_attempts value. For example, if max_attempts is set to ‘2’, and the restart fails on the first attempt, more than two restarts may be attempted.

What? "If the restart does not succeed within the configured window, this attempt doesn’t count toward the configured max_attempts value." Is "does not succeed" == "fails"?

So it means: "If the restart fails within the configured window, this attempt doesn’t count toward the configured max_attempts value."

So the failure has to happen after the window? So if it fails right away it will just retry endlessly? This makes no sense.

If this is the semantics there should be some sort of warning, maybe: "Beward that any rapid failure will make the docker daemon use all available CPU and disk on the machine".

[docker-robott]

There hasn't been any activity on this issue for a long time.
If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment.
If not, this issue will be closed in 14 days. This helps our maintainers focus on the active issues.

Prevent issues from auto-closing with a /lifecycle frozen comment.

/lifecycle stale

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

/lifecycle locked