-
Notifications
You must be signed in to change notification settings - Fork 639
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Group ownership in Docker image prevents running on OpenShift #307
Comments
I've fixed file ownership but it seems that ElasticSearch image has the same problem. So it fails on OpenShift. Please tell us if you successfully run TheHive on OpenShift (with ElasticSearch). |
Thanks for the quick fix @To-om ! I had it working yesterday using a custom image (just using your image with the required
Has something else changed at the same time? |
The latest version of the docker image uses TheHive 2.13 which need ElasticSearch 5.x. You can try the docker image certbdf/thehive:2.12.1-2 |
Awesome, thanks! Will the |
I forgot to update this file, I'll do it. |
docker-compose file has been tested and updated. |
Request Type
Bug /
Feature Requestsort of both, realistically
Work Environment
Problem Description
In the Dockerfile generated during the build, the permissions on
/opt/thehive
are specifically set to thedaemon
user on line 8:Currently, this prevents running this image on OpenShift since it uses randomised high UIDs to run the container.
This could be fixed by changing the directory to use the
root
(or0
) group, retaining thedaemon
user's ownership. That is:From what I can tell, this would not break any existing use cases but would allow it to run on OpenShift platforms unmodified.
Let me know if this change would be acceptable and I can open a PR.
Steps to Reproduce
certbdf/thehive
image in OpenShiftTo test resolution:
Possible Solutions
Change ownership on
/opt/thehive
directory todaemon:root
Complementary information
The same problem/change applies to Cortex as well, but I want to make sure this change would be accepted before I open an issue/PR there as well.
The text was updated successfully, but these errors were encountered: