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

Update Docker build for terrascan to use numeric UID #766

Closed
jlk opened this issue May 11, 2021 · 1 comment · Fixed by #773
Closed

Update Docker build for terrascan to use numeric UID #766

jlk opened this issue May 11, 2021 · 1 comment · Fixed by #773
Assignees
Labels
Projects

Comments

@jlk
Copy link
Contributor

jlk commented May 11, 2021

  • terrascan version: 1.5.0
  • Operating System: MacOS

Description

When developing helm chart, to follow best practices I'd like to set a securityContext of runAsNonRoot: true
Unfortunately, when the k8s deployment creates a pod, the following error is seen in pod details:

Events:
  Type     Reason     Age               From               Message
  ----     ------     ----              ----               -------
  Normal   Scheduled  13s               default-scheduler  Successfully assigned default/terrahook-7b8fd679ff-jsk5k to aks-agentpool-30212186-vmss000002
  Normal   Pulling    13s               kubelet            Pulling image "alpine/git"
  Normal   Pulled     12s               kubelet            Successfully pulled image "alpine/git"
  Normal   Created    12s               kubelet            Created container git-cloner
  Normal   Started    12s               kubelet            Started container git-cloner
  Normal   Pulled     9s (x2 over 10s)  kubelet            Container image "accurics/terrascan:1.5.0" already present on machine
  Warning  Failed     9s (x2 over 10s)  kubelet            Error: container has runAsNonRoot and image has non-numeric user (terrascan), cannot verify user is non-root

So looks like we need to change the Dockerfile to read

USER 101
@Rchanger
Copy link
Contributor

We can also set runAsUser field in helm configurations.

 runAsUser: 101

@Rchanger Rchanger added this to To do in Main Board via automation May 11, 2021
@Rchanger Rchanger moved this from To do to In progress in Main Board May 11, 2021
@Rchanger Rchanger linked a pull request May 12, 2021 that will close this issue
@Rchanger Rchanger moved this from In progress to Review in progress in Main Board May 12, 2021
Main Board automation moved this from Review in progress to Done May 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

Successfully merging a pull request may close this issue.

3 participants