Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docker-slim-sensor and traced executable never finish running on armhf #214

Open
ralight opened this issue Jul 21, 2021 · 0 comments
Open
Labels

Comments

@ralight
Copy link

ralight commented Jul 21, 2021

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.
@kcq kcq added the triage label Jul 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants