liquidmetal-dev / liquidmetal-dev/image-builder
Do ARM images properly
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 29
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
Right now they are just under experimental, but it should not be too tricky to do multi-arch image (just a couple of bits differ, mostly filename args).
Also for both ARM and 86 images we should try to put the kernel bin **in the same location** because right now that is another thing you need to remember to change when you use a different arch and it is very annoying.
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 by locating the image build arguments and kernel binary path used by the ARM and x86 image flows, then compare their architecture-specific filename handling. Done means both architectures build as multi-arch images and use the same kernel location, without requiring an architecture-specific path change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, dockerfile
- Domain
- build-system, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100