solving ostree fsck errors when using container images?

[miabbott]

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]

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.