Run ActiveMQ container as a non-root user#1648
Run ActiveMQ container as a non-root user#1648pradeep85841 wants to merge 5 commits intoapache:mainfrom
Conversation
- HEALTHCHECK uses Jolokia search on Broker MBean - Ensures broker is running and accessible - Auth and Origin headers included for Jolokia security - Docker CI-ready and deterministic
- Create a dedicated 'activemq' user and group - Ensure ActiveMQ home directory is owned by this user - Drop root privileges before starting the broker This improves container security by avoiding running the process as root, aligning with Docker best practices.
|
FYI a similar PR has been created a few months ago. I will take a look on this one. |
|
The test has been merged already as part of the other PR. So you probably want to rebase this one. What do you think? |
|
Thanks, that’s helpful. I’ll rebase this PR on top of the merged changes so it aligns with the current Docker improvements. Let me know if you’d prefer a different approach. |
|
@pradeep85841 I gonna review the PR tomorrow. Thanks ! |
|
FYI, here's the corresponding Jira: https://issues.apache.org/jira/browse/AMQ-9588 |
There was a problem hiding this comment.
This is unrelated to the Docker image.
Can you please remove this file from the PR ?
There was a problem hiding this comment.
The PR should have been rebased but it won't matter to much here because the test was part of another PR that got merged last week #1631
I think we are good to go.
|
Superseded by #1665 |
Summary
This PR modifies the Dockerfile to run the ActiveMQ container
as a dedicated non-root user, improving security and following
Docker best practices.
Changes
Testing