-
Notifications
You must be signed in to change notification settings - Fork 284
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
solving ostree fsck
errors when using container images?
#3092
Comments
Seconding this. I switched to Universal Blue when a bug affecting Fedora Atomic composes resulted in no updates for an extended period of time, and then switched back when the bug was fixed. I ran Since it isn't critical, I'm leaving it be for now, but this may cause problems in the future if not mitigated. Since |
via https://www.reddit.com/r/Fedora/comments/17qrqra/i_cannot_touch_this_issue_ostree_fsck_encounters/
The user there deployed a Universal Blue derived container image and
ostree fsck
is finding corruption.After going through the suggestions on how to resolve it, it seems like the tooling previously used to address this problem doesn't fully support the container image format.
Perhaps this is just an example of #2499?
The text was updated successfully, but these errors were encountered: