Fix: Container Running with Dangerous Root Access Permissions in Dockerfile

[kira-offgrid]

Context and Purpose:

This PR automatically remediates a security vulnerability:

• Description: By not specifying a USER, a program in the container may run as 'root'. This is a security hazard. If an attacker can control a process running as root, they may have control over the container. Ensure that the last USER in a Dockerfile is a USER other than 'root'.
• Rule ID: dockerfile.security.missing-user.missing-user
• Severity: MEDIUM
• File: Dockerfile
• Lines Affected: 23 - 23

This change is necessary to protect the application from potential security risks associated with this vulnerability.

Solution Implemented:

The automated remediation process has applied the necessary changes to the affected code in Dockerfile to resolve the identified issue.

Please review the changes to ensure they are correct and integrate as expected.

[Copilot]

Pull Request Overview

This PR adds a non-root user to the Dockerfile to address a security vulnerability where the container would otherwise run as root.

• Create a system user langbot
• Switch container runtime to the langbot user

Comments suppressed due to low confidence (1)

Dockerfile:24

• Ensure that any application files and directories are owned or accessible by the langbot user before switching users. You can add a chown -R langbot:langbot /app (or your working directory) prior to USER langbot to avoid permission issues at runtime.

USER langbot