⬆️ Update just-containers/s6-overlay to v3.2.0.0 #154
Merged
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.
This PR contains the following updates:
3.1.6.2
->3.2.0.0
Release Notes
just-containers/s6-overlay (just-containers/s6-overlay)
v3.2.0.0
Compare Source
if the services took more than 5 seconds to be brought up, they would
fail; the intent was to detect hanged containers (waiting on a dysfunctional
network connection, for instance) and make them fail early, but it has
proven to create more problems than it was solving - so the timeout has
been removed. If you need it, you can, as before, use the
S6_CMD_WAIT_FOR_SERVICES_MAXTIME
variable.
able to use s6-overlay in containers created by Kubernetes, for instance.
Configuration
📅 Schedule: Branch creation - "before 2am" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.