fix SdkDockerClient recovery if docker socket not available initially #8279
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.
Currently, if the Docker socket is not available at the start of LocalStack, the initialization of the
SdkDockerClient
fails and the client will not recover during the runtime of LocalStack.This PR changes this behavior such that:
DOCKER_SDK_DEFAULT_RETRIES
which allows configuring the amount of retries when initializing the client.This addresses localstack/helm-charts#21.