-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Loadgenerator failing to start in Mac M1 #178
Comments
thank you @julianocosta89 for creating the bug report! |
hi, I was able to sucessfully run Not sure if this is optimal/desired change, and how it affects other platforms. |
worth noting that I'm running an M1 and not seeing this issue 🤔 |
Thanks for taking a look @Kiedro! |
@GaryPWhite I believe you already have a python:3.10-slim cached and docker is not trying to pull the latest one. Could you try to delete it and run the compose build again? |
deleted, ran again, everything broke :) I tried the not-slim image and I'll reference it in my ongoing PR! |
I had encoutered the same problem, I fix it by #126 |
Can we close this? @Frapschen is your solution something we can add to the repo? |
@cartersocha, the solution is part of @GaryPWhite's PR. |
good to close this now I think! PR is merged! |
Bug Report
Which version of the demo you are using?
f8db21d7ce011c965d5edd6f058429eae7e2d4e3
Symptom
What is the expected behavior?
We expect the demo to start and have load automatically.
What is the actual behavior?
Loadgen failing to start.
Reproduce
docker compose up
in a Mac with M1.Additional Context
Log:
The text was updated successfully, but these errors were encountered: