-
Notifications
You must be signed in to change notification settings - Fork 4
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
Local run fails #77
Comments
There is not a label identifying the kind of this issue. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/kind bug |
@FedeDP: The label(s) In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Regarding this last point, |
/close Added more bullet points to the tracking issue: falcosecurity/libs#1224 |
@FedeDP: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Describe the bug
I was testing new
ghcr
images, and i discovered that we are no more able to runkernel-testing
framework locally because of:Basically,
weaveworks/ignite:dev
was shutted down; our libs tests do work because that image is cached on the cncf nodes where the tests run.IMHO we should at the very least compeltely quit relying on
weaveworks
images.We use:
in
ansible-playbooks/group_vars/all/vars.yml
and
in builder and modernprobe-builder
Dockerfile.kernel
.Also, we should patch
https://github.com/therealbobo/ignite
to use our ownweaveworks/ignite:dev
image as default (or a parameter could be enforced using--sandbox-image
cli option).The text was updated successfully, but these errors were encountered: