slimtoolkit / slimtoolkit/slim
docker-slim-sensor and traced executable never finish running on armhf
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.4k
- Forks
- 841
- PR merge metrics
- No merged PRs in 30d
Description
Expected Behavior
When I run docker-slim build ... on an armhf host (Raspberry Pi in this case)... it works :)
Actual Behavior
I see that docker-slim-sensor and the executable being traced take up a large percentage of CPU time, and never finish executing. In my example one of the first processes to run is openssl rand 32 which takes about 3ms on my Pi when running normally. I killed it after about 5 hours of high cpu use when running under docker slim.
I've tested the binaries for 1.30.0 and they are fine, the problem is present in 1.32.0. I didn't test 1.31.0 because there weren't binaries available.
Steps to Reproduce the Problem
This small image demonstrates the problem for me:
docker-slim build ralight/slimtest:latest --show-blogs --show-clogs --http-probe=false
Specifications
- Platform: Raspbian GNU/Linux 10 (buster) on a Raspberry Pi 4.
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
Start by reproducing docker-slim build ralight/slimtest:latest --show-blogs --show-clogs --http-probe=false on the specified armhf Raspberry Pi environment, focusing on docker-slim-sensor and the traced executable. Compare behavior with the 1.30.0 and 1.32.0 binaries; done means the command and traced processes finish normally on armhf.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- devops, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100