Description
As of now the secure ozone cluster uses a custom image which is not based on the apache/hadoop-runner image. There are multiple problems with that:
1. multiple script files which are maintained in the docker-hadoop-runner branch are copied and duplicated in hadoop-ozone/dist/src/main/compose/ozonesecure/docker-image/runner/scripts
2. The user of the image is root. It creates core-site.xml/hdfs-site.xml/ozone-site.xml which root user which prevents to run all the default smoke tests
3. To build the base image with each build takes more time
I propose to check what is missing from the apache/hadoop-ozone base image, add it and use that one.
I marked it critical because 2): it breaks the run of the the acceptance test suit.
Attachments
Attachments
Issue Links
- causes
-
HDDS-1190 Fix jdk 11 issue for ozonesecure base image and docker-compose
- Resolved