sbt/sbt-native-packager

Root user compliance in twistlock when we build the image

Open

#1,452 opened on Aug 27, 2021

View on GitHub
 (1 comment) (1 reaction) (0 assignees)Scala (1,593 stars) (439 forks)batch import
dockerhelp wanted

Description

Expected behaviour

When we run sbt docker:publishLocal it is creating the image with default user demiourgos728. When we run the pod with same image it is running with user demiourgos728, there should not be any compliance issue related to non-root user.

Actual behaviour

When we run the pod with same image it is running with user demiourgos728, but the compliance issue on twistlock says that we are not running with non-root user.

Information

  • What sbt version : 1.3.13
  • What is your build system (e.g. Ubuntu, MacOS, Windows, Debian ) : centos7
  • What package are you building (e.g. docker, rpm, ...) : docker
  • What version has your build tool (find out with e.g. rpm --version) :
  • What is your target system (e.g. Ubuntu 16.04, CentOS 7) : adoptopenjdk/openjdk11:jdk-11.0.11_9-alpine

Contributor guide

Tech stack
scaladocker
Domain
devops
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
sbt native packagerDockerTwistlock compliance scanning
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate the sbt native packager Docker plugin configuration for default user settings. Look at how the Dockerfile is generated during 'docker:publishLocal'. Check if the USER instruction is missing or set incorrectly. Review the documentation for configuring the Docker daemon user. Consider testing with a minimal build to reproduce the compliance issue.