-
Notifications
You must be signed in to change notification settings - Fork 3
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
[Bug/Feature Request]: Fails to run using Rancher Desktop - Rancher Desktop Support? #9
Comments
For reference this appears to be caused by this upstream issue: rancher-sandbox/rancher-desktop#3239 |
Thanks for flagging this @syserr0r, and for the details reproduction steps! I was able to replicate the issue you reported, and found that there were two areas that needed adjusting. First of all, I replaced the Please could you let me know if this resolves it for you?
If so, I'll perform a bit more testing in some different environments, but should be able to get this pushed out asap. Thanks again! From there, you can open a repo with something supported by Checkov, and see if you get any errors. Edit: In testing for myself, --tty/-t was not required, and actually created some noise |
Sorry for the delay in getting back to you, it has been kinda hectic around here 😅 I wasn't sure which version of node/npm to use, so I used the latest lts (node v20.18.0/npm v10.8.2). Pressing F5 launches a new VSCode window and presents the following error pop-up: Attempting to troubleshoot further:
The logs from
Restarting debugging (F5) for the extension, opening a test python file and running a checkov scan results in this from
Looks good to me 👍 |
@XargsUK any news on when the fix for this might be published? Is there a blocker I can help with? |
Going to be releasing this now 👍🏼 Been testing over the past couple of weeks, happy with it. |
Python Version
n/a
Checkov Installation Method
docker
CheckovPrismaless Version
1.0.107
VSCode Version
1.93.1
Operating System
Windows 10
Description of the Bug
CheckovPrismaless fails to run the docker command - every file save where Checkov would be called results in a "Any troubles? We can help you figure out what happened" notification.
Enabling debugging and looking at the logs I can see CheckovPrismaless does not correctly get the version from docker, see the following output when calling the "Install or Update" command:
When CheckovPrismaless then tries to run it attempts to docker run with the previously found empty version string, resulting in trying to run the image
bridgecrew/checkov:
which is invalid, this can be seen as follows:Running the command manually in the WSL2 terminal we can see no output:
Re-running the command with the
-it
flags gives us the correct output:Running both commands on a linux VM with docker installed we can see they both output the version string (so no adverse affects to adding the
-it
flag and explains why it would work with docker):Steps to Reproduce
The text was updated successfully, but these errors were encountered: