This Pull Request was automatically generated by Jit. We highly recommend that you check the suggestion and make
sure everything works before merging it. An explanation of the suggested changes is available below.
What changes are proposed in this PR?
First of all, check if your container is running as a root user. In most of the cases, you can do it by running a command like this: docker run <image> whoami. If it returns root, then you should consider using a non-root user, by following one of the next steps:
If a non-root user already exists in your container, consider using it.
If not, you can create a new user by adding a USER command to the Dockerfile, with a non-root user as argument, for example: USER <non-root-user-name>.
Why are these changes important?
If you don't specify at least 1 USER command in the Dockerfile, the container will run as root. If a security vulnerability is exploited in the root container, an attacker could gain complete control over the host system and any other containers running on it, potentially leading to devastating consequences.
Specify a non-root user in your Dockerfile
This Pull Request was automatically generated by Jit. We highly recommend that you check the suggestion and make sure everything works before merging it. An explanation of the suggested changes is available below.
What changes are proposed in this PR?
docker run <image> whoami. If it returnsroot, then you should consider using a non-root user, by following one of the next steps:USERcommand to the Dockerfile, with a non-root user as argument, for example:USER <non-root-user-name>.Why are these changes important?
If you don't specify at least 1 USER command in the Dockerfile, the container will run as root. If a security vulnerability is exploited in the root container, an attacker could gain complete control over the host system and any other containers running on it, potentially leading to devastating consequences.