Skip to content
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

Open
miabbott opened this issue Nov 9, 2023 · 1 comment
Open

solving ostree fsck errors when using container images? #3092

miabbott opened this issue Nov 9, 2023 · 1 comment

Comments

@miabbott
Copy link
Collaborator

miabbott commented Nov 9, 2023

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?

@muelsyse-az
Copy link

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 sudo ostree fsck and then later sudo ostree fsck and ran into the exact same issues as the Reddit post.

Since it isn't critical, I'm leaving it be for now, but this may cause problems in the future if not mitigated. Since ostree fsck is the one finding the corruption, I found it suitable to add a comment here. However, I think that this is also an rpm-ostree issue, as rpm-ostree was the tool used for rebasing, and also I have a feeling that this is related to the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants