-
Notifications
You must be signed in to change notification settings - Fork 166
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
Cannot run k6-operator "exec /manager: exec format error" #383
Comments
Not sure if related, but https://github.com/grafana/k6-operator/blob/main/config/manager/manager.yaml#L30 |
Tried spinning up a local cluster using k6.operator.mov |
This is ARM arch, right? If so, we have an issue for that here #187 I'll try to ping the author there as it's been awhile. But he has the image built there: could you please check if it works for you? It'd be helpful to confirm for your platform. |
Hi, @danielfigueiredo you may try this repo (until it's merged to upstream), and pls let me know if it works out for you. Example TestRun manifest: apiVersion: k6.io/v1alpha1
kind: TestRun
metadata:
name: closed-test
spec:
parallelism: 5
starter:
image: ghcr.io/audacioustux/k6-operator:starter-latest
imagePullPolicy: Always
runner:
image: ghcr.io/audacioustux/k6-operator:runner-latest
imagePullPolicy: Always
arguments: --out cloud
script:
configMap:
name: closed-lt
file: index.js |
@audacioustux your branch + docker img does work for me! 🎉 The only thing I couldn't test was the install via helm, I just ran Thanks all |
Perfect; thank you, @danielfigueiredo, for checking! |
I think it makes sense for me to close this issue given we are already tracking the error here #187 ? I'll subscribe and follow up on the other PR/Issues 😄 |
Brief summary
I've tried installing the
k6-operator
both via helm (latst version3.5.0.
) or viamake deploy
using latest master. Both way produce the exact same error.The manager pod fails to start with error, however
kube-rbac-proxy
start just fine.I'm running on a mac
aarch64-darwin
systemk6-operator version or image
latest master
Helm chart version (if applicable)
3.5.0
TestRun / PrivateLoadZone YAML
Other environment details (if applicable)
No response
Steps to reproduce the problem
make deploy
of master orhelm install ....
as perREADME.md
)k6-operator-controller-manager
, status isCrashLoopBackOff
No errors during install or anything, it only fails booting up.
Expected behaviour
The resources required by the
k6-operator
bootstraps fine and reliably when using later or main versions.Actual behaviour
manager
status on fresh install on fresh cluster isCrashLoopBackOff
with errormanager exec /manager: exec format error
The text was updated successfully, but these errors were encountered: