search

genuinetools / img

Standalone, daemon-less, unprivileged Dockerfile and OCI compatible container image builder.
https://blog.jessfraz.com/post/building-container-images-securely-on-kubernetes/
MIT License
3.89k stars 230 forks source link

Some images cannot be unpacked #224

Open jeromegn opened 5 years ago

jeromegn commented 5 years ago

Not entirely sure what's happening here, but it looks like some folder structure is missing.

$ img pull h2non/imaginary
Pulling h2non/imaginary...
Pulled: sha256:b7127656b47f01cb9a88cd3e82aca6d2b1e480ecd79345964271c5dddb852d5e
Size: 88.3MiB

$ img unpack -d h2non/imaginary
DEBU[0000] using backend: native
DEBU[0000] Unpacking layer sha256:22dc81ace0ea2f45ad67b790cddad29a45e206d51db0af826dc9495ba21a0b06
extracting tar for sha256:22dc81ace0ea2f45ad67b790cddad29a45e206d51db0af826dc9495ba21a0b06 to directory /home/jerome/src/github.com/superfly/run-vm-run/rootfs failed: chmod /home/jerome/src/github.com/superfly/run-vm-run/rootfs/dev/agpgart: no such file or directory

Seems to work for most other docker images I tested.

issue-label-bot[bot] commented 5 years ago

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.90. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!

Links: dashboard, app homepage and code for this bot.

hamelsmu commented 5 years ago

@jeromegn we are about to launch the issue-label-bot more publicly. Do you mind if I use a screenshot of this issue in a blog post? Thank you

jeromegn commented 5 years ago

@hamelsmu sure, go ahead.