You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use the kics docker image for running tests and it is no longer working as in #7292 the dockerfile was updated to run as a specific user. It is not clear why this change was made so I am hoping that it can be reverted.
In the getting started documentation the first suggestion is to run kics as a docker container and mount a volume as a container. As in the example command, you will also most likely output a report to that volume. However, the user that is now running the container does not have access to that volume, and that is a very hard problem to solve, especially when the volume mount is a github repo used by multiple developers and your CI system. Can we get the change reverted so the container runs as root again? There is already a solution for running the container as a specific user (using the UBI based images) and I'm assuming this change wasn't meant to break the workflow I described above.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We use the kics docker image for running tests and it is no longer working as in #7292 the dockerfile was updated to run as a specific user. It is not clear why this change was made so I am hoping that it can be reverted.
In the getting started documentation the first suggestion is to run kics as a docker container and mount a volume as a container. As in the example command, you will also most likely output a report to that volume. However, the user that is now running the container does not have access to that volume, and that is a very hard problem to solve, especially when the volume mount is a github repo used by multiple developers and your CI system. Can we get the change reverted so the container runs as root again? There is already a solution for running the container as a specific user (using the UBI based images) and I'm assuming this change wasn't meant to break the workflow I described above.
Beta Was this translation helpful? Give feedback.
All reactions