-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Partial match in volume discovery can lead to endless volume removal loop #2207
Comments
This should fix it:
Better yet to use labels somehow: |
Previous regex would recognize non balena volumes with partial matches. Closes: #2207
When non-balena managed docker volumes are present that partially match the appId_volumeName regular expression, the partial name will be used incorrectly as the full name by the supervisor. Contributed-by: @thomaswiese0 Change-type: patch Closes: #2207
Hi @thomaswiese0 thank you for the issue and the correction. You are correct that using labels is the right approach, unfortunately the only way to modify volumes is to recreate them which we cannot do without destroying data. We are considering a volume migration procedure at which point we should be able to sanitize volume metadata. In the meantime, I've created PR #2218 with your patch Thanks again |
When non-balena managed docker volumes are present that partially match the appId_volumeName regular expression, the partial name will be used incorrectly as the full name by the supervisor. Change-type: patch Contributed-by: @thomaswiese0 Closes: #2207
If non balena-managed volumes are present that partially match the
<appId>_<volumeName>
expression indeconstructDockerName
, e.g.,a2_b
, the supervisor will go into an endless loop trying to remove a volume with name2_b
(the partial match). The device becomes unusable.The text was updated successfully, but these errors were encountered: