Skip to content
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

CIS-DI-0010 Suspicious ENV key found #196

Closed
zfLQ2qx2 opened this issue Aug 8, 2022 · 1 comment
Closed

CIS-DI-0010 Suspicious ENV key found #196

zfLQ2qx2 opened this issue Aug 8, 2022 · 1 comment
Labels
question Further information is requested

Comments

@zfLQ2qx2
Copy link

zfLQ2qx2 commented Aug 8, 2022

We recently updated from dockle 0.4.2 to 0.4.6 and started getting a lot of CIS-DI-0010 "Suspicious ENV key found" issues.

They are absolutely legitimate finds, if I do "docker history --no-trunc " I can see tokens passed in as ARGs embedded in the image. Hats off to Dockle for finding this before someone else did!

However what is not clear to me is how to remediate the issue. There wasn't anything in the Dockle wiki that spoke to this specifically and I didn't see where anyone else had asked in an issue. Could someone give me an idea what to do?

@zfLQ2qx2 zfLQ2qx2 added the question Further information is requested label Aug 8, 2022
@PeterMosmans
Copy link
Contributor

Hi @zfLQ2qx2 - do you mean how to suppress the warning, or how to mitigate the ENV findings?
For the former, you can use the --ignore CIS-DI-0010 prefix after the dockle command, before the name of the image.
For the latter, it's difficult to say without seeing the images, but it sounds like multi-stage builds would solve that issue, as the production-ready image can be rid of all 'build' artifacts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants