RANGER-4746: Change default docker build to use JDK 8 (#309)

apache · Apr 9, 2024 · f3637ac · f3637ac
1 parent 4abb993
commit f3637ac
Show file tree

Hide file tree

Showing 2 changed files with 9 additions and 5 deletions.
diff --git a/dev-support/ranger-docker/.env b/dev-support/ranger-docker/.env
@@ -6,7 +6,7 @@ PROFILE=
 BUILD_OPTS=
 
 # To build Trino plugins package, use following PROFILE
-PROFILE=ranger-jdk11,!all,!linux
+# PROFILE=ranger-jdk11,!all,!linux
 
 # Java version for RangerBase image.
 # This image gets used as base docker image for all images.
@@ -16,7 +16,7 @@ RANGER_BASE_JAVA_VERSION=8
 # Java version to use to build Apache Ranger
 # Valid values: 8, 11, 17
 # Trino builds on jdk 11 and above
-RANGER_BUILD_JAVA_VERSION=11
+RANGER_BUILD_JAVA_VERSION=8
 
 # Java version to use to run Ranger Admin server
 # Valid values: 8, 11, 17

diff --git a/dev-support/ranger-docker/README.md b/dev-support/ranger-docker/README.md
@@ -66,14 +66,18 @@ Docker files in this folder create docker images and run them to build Apache Ra
          ~~~
 7. To enable file based sync source for usersync execute: ```export ENABLE_FILE_SYNC_SOURCE=true```
 
-8. Execute following command to start Ranger, Ranger enabled HDFS/YARN/HBase/Hive/Kafka/Knox and dependent services (Solr, DB) in containers:
+8. Execute following command to start Ranger, Ranger Usersync, Ranger Tagsync, Ranger enabled HDFS/YARN/HBase/Hive/Kafka/Knox and dependent services (Solr, DB) in containers:
    ~~~
-   docker-compose -f docker-compose.ranger-base.yml -f docker-compose.ranger.yml -f docker-compose.ranger-${RANGER_DB_TYPE}.yml -f docker-compose.ranger-usersync.yml -f docker-compose.ranger-tagsync.yml -f docker-compose.ranger-kms.yml -f docker-compose.ranger-hadoop.yml -f docker-compose.ranger-hbase.yml -f docker-compose.ranger-kafka.yml -f docker-compose.ranger-hive.yml -f docker-compose.ranger-trino.yml -f docker-compose.ranger-knox.yml up -d
+   docker-compose -f docker-compose.ranger-base.yml -f docker-compose.ranger.yml -f docker-compose.ranger-${RANGER_DB_TYPE}.yml -f docker-compose.ranger-usersync.yml -f docker-compose.ranger-tagsync.yml -f docker-compose.ranger-kms.yml -f docker-compose.ranger-hadoop.yml -f docker-compose.ranger-hbase.yml -f docker-compose.ranger-kafka.yml -f docker-compose.ranger-hive.yml -f docker-compose.ranger-knox.yml up -d
    ~~~
 
 	- valid values for RANGER_DB_TYPE: mysql or postgres
+9. To run ranger enabled Trino in containers (Requires docker build with JDK 11):
+   ~~~
+   docker-compose -f docker-compose.ranger-base.yml -f docker-compose.ranger.yml -f docker-compose.ranger-${RANGER_DB_TYPE}.yml -f docker-compose.ranger-trino.yml up -d
+   ~~~
 
-9. To rebuild specific images and start containers with the new image, use following command:
+10. To rebuild specific images and start containers with the new image, use following command:
    ~~~
    docker-compose -f docker-compose.ranger-base.yml -f docker-compose.ranger.yml -f docker-compose.ranger-usersync.yml -f docker-compose.ranger-tagsync.yml -f docker-compose.ranger-kms.yml -f docker-compose.ranger-hadoop.yml -f docker-compose.ranger-hbase.yml -f docker-compose.ranger-kafka.yml -f docker-compose.ranger-hive.yml -f docker-compose.ranger-trino.yml -f docker-compose.ranger-knox.yml up -d --no-deps --force-recreate --build <service-1> <service-2>
    ~~~