Figure out vhd/raw issue with Hydra
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 84
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
We had to revert https://github.com/NixOS/nixpkgs/pull/511177 as raw image is too big for Hydra..
We should start building images in GHA. but that doesn't work for aarch64 due to lack of nested virt IIRC, which means we have to move to repart #354 but that is blocked on #322 which we cant make progress on as EC2 x86 bare metal instances don't have EFI support but many people use them as they reliably support /dev/kvm. 8th generation instances also support kvm but not all, so a lot of people use these bare metal instances for nix builders....
other options is to store the output compressed in Hydra? or to convert from VHD to raw after fetching in Hydra?
Other fix: move the AWS image back to auto size instead of fixed size. That should make it smaller than the hydra limit too I think
Lots of interdependent mess here T_T
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reverted PR #511177 and the Hydra image-size failure, then review the listed GHA, repart, compression/conversion, and auto-size options alongside blockers #354 and #322. Done means selecting and documenting an implementable path that produces an image within Hydra’s limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, github-actions, python
- Domain
- build-system, cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100