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

ociruntime: fix blocking on unknown tar header #8017

Closed
wants to merge 3 commits into from

Conversation

sluongng
Copy link
Contributor

@sluongng sluongng commented Dec 5, 2024

It seems like our "executor-docker-default" image contains quite a few
/dev/* entries in a layer on the image.

These are either block or character devices that don't do much on the
container itself and should be safe to ignore.

@@ -1369,7 +1369,7 @@ func downloadLayer(ctx context.Context, layer ctr.Layer, destDir string) error {
return status.UnavailableErrorf("chown file: %s", err)
}
default:
return status.UnavailableErrorf("unsupported tar entry type %q", header.Typeflag)
log.CtxWarningf(ctx, "Ignoring unsupported tar header %q type %q in oci layer", header.Name, header.Typeflag)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: I think these warnings will be spammy. Would it work to explicitly skip character and block devices?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

or alternatively just log at info level for now.

@sluongng sluongng marked this pull request as draft December 5, 2024 16:53
@sluongng
Copy link
Contributor Author

sluongng commented Dec 5, 2024

turning this to draft to do a bit more testing.

We reverted the original PR instead.

@sluongng sluongng force-pushed the sluongng/fix-device-tar-unpack branch from 30405e1 to 9f4b3cd Compare December 6, 2024 16:02
@sluongng
Copy link
Contributor Author

sluongng commented Dec 6, 2024

Replacing this PR with #8023

@sluongng sluongng closed this Dec 6, 2024
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

Successfully merging this pull request may close these issues.

2 participants