slimtoolkit / slimtoolkit/slim
Minified image doesn't retain the platform information from the original image
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.4k
- Forks
- 840
- PR merge metrics
- No merged PRs in 30d
Description
From Fredrik Svensson on Slack:
I'm using multiarch/qemu-user-static to generate/run armhf images on an amd64 host.
So the original image has platform=linux/arm/v7 but the generated image gets platform=linux/amd64.
docker-slim works fine, the image is possible to run although docker complains the architecture is wrong
when running on the armhf device. Is there some way to set platform for the image as you can do
with docker build --platform=linux/arm/v7?
Contributor guide
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
No files or tests are named. Start by tracing how image metadata is handled during minification and compare the original and generated platform values, using the multiarch/qemu-user-static scenario described. Done means the generated image retains the original linux/arm/v7 platform instead of reporting linux/amd64.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100