Run FileProcessor as the base image’s non-root user

[Copilot]

This updates the Linux container image to stop running FileProcessor as root, addressing the container hardening issue raised on FileProcessor/Dockerfile. It also aligns the runtime user with the base image’s expected non-root account instead of introducing a custom one.

• Runtime user

  • Switch the final image to run as the base image’s built-in non-root user: app
  • Avoid creating a second service account in the final stage

• Filesystem ownership

  • Ensure /home/txnproc exists in the final image
  • Reassign /app and /home/txnproc to app:app so the service can access its runtime paths for config, logs, and file processing

• Dockerfile change

  • Replace custom user creation with ownership adjustment and USER app

FROM mkdir AS final
WORKDIR /app
COPY --from=publish /app/publish .
RUN mkdir -p /home/txnproc \
    && chown -R app:app /app /home/txnproc
USER app
ENTRYPOINT ["dotnet", "FileProcessor.dll"]

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[Security] By not specifying a USER, a program in the container may run as 'root'. This is a security hazard.</issue_title>
<issue_description>Codacy ID: 7139f3b4b22c59b0fed7f38c85f9bef4

File: FileProcessor/Dockerfile
Line: 30
Rule: Security (High)
Commit: 552b6744021b018ff322b894db9d833640ed4a84

Code Snippet:

ENTRYPOINT ["dotnet", "FileProcessor.dll"] 
```</issue_description>

## Comments on the Issue (you are @copilot in this section)

<comments>
</comments>

• Fixes [Security] By not specifying a USER, a program in the container may run as 'root'. This is a security hazard. #683

---

📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.