velero: bugfix: BackOffLimitExceeded GLIBC not found #117
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixes BackfOffLimit Exceeded due to libc.so.6: version `GLIBC_2.33' not found, as mentioned upstream at vmware-tanzu/helm-charts#550
velero: bugfix: BackOffLimitExceeded GLIBC not found Velero
|
... by bumping up versions in README to 0.2.2? |
baixiac
approved these changes
Apr 9, 2024
|
@baixiac is the opened issue fine? |
|
Yes @jdaln, and feel free to resolve it when the upstream gets fixed. |
|
Hi @Bdegraaf1234 @keyvaann @blootsvoets . |
keyvaann
added a commit
to RADAR-base/RADAR-Kubernetes
that referenced
this pull request
May 2, 2024
pvannierop
pushed a commit
to RADAR-base/RADAR-Kubernetes
that referenced
this pull request
Oct 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description of the change
Fixes BackfOffLimit Exceeded due to libc.so.6: version `GLIBC_2.33' not found, as mentioned upstream at vmware-tanzu/helm-charts#550
Benefits
One will be able to deploy RADAR with Velero because it is currently not possible. This was an unnoticed regression.
Possible drawbacks
Uses a specific version of Debian but, because this is in an init container, it does not involve security issues in the long term.
Applicable issues
Additional information
Checklist
Chart.yamlaccording to semver.