-
Notifications
You must be signed in to change notification settings - Fork 11
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
Update minio version #155
Comments
Thanks for raising this! It should be addressed by #160 |
@klutchell - looks like no good deed goes unpunished...
Looks like https://github.com/balena-io/open-balena/blob/ea07d43c5c7e98bb8b11c808b12428a46019c8d5/compose/services.yml#L8C8-L8C8 needs to be updated to: volumes:
...
s3:
driver: local And the fun from https://min.io/docs/minio/linux/operations/install-deploy-manage/migrate-fs-gateway.html For my local test instance, the following fixed it - but I'm not sure how to generically detect that this needs to happen: systemctl stop open-balena-s3
rm -rf /export/.minio.sys
systemctl start open-balena-s3 When minio was restarted it seems to have rebuilt its .minio.sys folder in the way it wanted. |
Thanks for checking! I'll revert to a release before that change until we can add some tests to this repo, and some migration steps to open-balena. |
As of the day this issue was created, the latest minio version is
RELEASE.2023-08-29T23-07-35Z
, but the Dockerfile in this repo is still making use ofRELEASE.2022-05-04T07-45-27Z
- which is now ~15 months old. Minio has addressed at least 7 CVEs over this time.The text was updated successfully, but these errors were encountered: