-
Notifications
You must be signed in to change notification settings - Fork 17
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
failed to compile fetched bundle #1546
Comments
The workaround is to
|
thx |
After some more investigation, I am able to reproduce it locally: cnspec scan local -f cnspec-policies/core/mondoo-kubernetes-security.mql.yaml
FTL failed to resolve policies error="failed to compile bundle: failed to compile filters for query //local.cnspec.io/run/local-execution/queries/mondoo-kubernetes-security-pod-runasnonroot\nfailed to compile filters for query //local.cnspec.io/run/local-execution/queries/mondoo-kubernetes-security-cronjob-runasnonroot\nfailed to compile filters for query //local.cnspec.io/run/local-execution/queries/mondoo-kubernetes-security-job-runasnonroot" The problem is not happening on macOS or Windows. It it is also not related to registry as the problem seems to be located in the Kubernetes policy itself. |
This problem only happens when you are on a Linux machine and the k8s provider is not installed. To mitigate the error without without manually downloading the policies, just manually install the provider:
|
Since the issue is only happening when k8s provider is not installed, the user targets linux, we disabled the k8s policy as default policy in our registry for now mondoohq/cnspec-policies#470. As a followup, we are going to have a discussion what the default behavior should be:
|
What is not working as you expected it?
Start a fresh container and install cnspec:
Where on the platform does it happen?
It happens on all platforms where no authentication to the Mondoo platform is avaiable.
How do we replicate the issue?
Expected behavior (i.e. solution)
Scan runs through
Other Comments
The text was updated successfully, but these errors were encountered: