[Bug]: Files larger than 128 GiB cannot be unpacked into an ext4 image

Open
#921 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
swift

Research direction

Start by reproducing the issue with bin/container image load --input large-image.tar, then trace the image-unpacking path for the 128 GiB file-size limit and ext4 image handling. Done means a file larger than 128 GiB can be unpacked when disk space allows, while insufficient disk space still produces an error.

Written by the indexing model from the issue text.

Description

I have done the following
  • I have searched the existing issues
  • If possible, I've reproduced the issue using the 'main' branch of this project
Steps to reproduce
  1. Create an image with a single file above 128 GiB.
  2. Run:
bin/container image load --input large-image.tar
Current behavior
Error: 137439084544 exceeds max file size (128 GiB)
Expected behavior

No error, but only if unpacking wouldn't run out of disk space.

Environment
OS: macOS
Code of Conduct
  • I agree to follow this project's Code of Conduct
Dominant language
Swift
Stars
8.9k
Forks
360
Avg merge
1d 18h
Merged PRs (30d)
16

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apple/containerization

All issues in apple/containerization

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.