docker::run: make systemd rate-limits configurable #1030
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR makes it possible to configure systemd rate-limiting parameters (StartLimitIntervalSec and StartLimitBurst) in unit files created by docker::run.
Why is this needed?
Some container workloads may crash repeatedly on startup due to temporary conditions.
Without configurable StartLimit values, systemd may delay or prevent restarts too early.
This patch gives users control over these limits to better suit their use case.
Changes
Added two new optional parameters to docker::run:
start_limit_interval_sec
andstart_limit_burst
Added the same two optional parameters to the main docker class for global configuration:
start_limit_interval_sec
andstart_limit_burst
Checklist
puppet apply
)