Skip to content

ostree-ext/tar: Unset G_MESSAGES_DEBUG before spawning ostree commit #1917

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.

Sign up for GitHub

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

Merged
cgwalters merged 1 commit into from
Jan 15, 2026
Merged

ostree-ext/tar: Unset G_MESSAGES_DEBUG before spawning ostree commit #1917

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions crates/ostree-ext/src/tar/write.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -400,6 +400,12 @@ pub async fn write_tar(
None
};
let mut c = std::process::Command::new("ostree");
// Unset G_MESSAGES_DEBUG to prevent GLib debug messages from corrupting stdout.
// When G_MESSAGES_DEBUG is set (e.g., "all"), GLib and OSTree emit debug messages
// to stdout instead of stderr, which corrupts the commit hash we parse from
// the subprocess output. This causes derived layer content to be silently lost
// during container imports.
c.env_remove("G_MESSAGES_DEBUG");
Comment thread
jmarrero marked this conversation as resolved.
let repofd = repo.dfd_as_file()?;
let repofd: Arc<io_lifetimes::OwnedFd> = Arc::new(repofd.into());
{
Expand Down
Loading