# Java 11 or higher is required to run Dremio

**URL:** <https://community.dremio.com/t/java-11-or-higher-is-required-to-run-dremio/12907>\
**Category:** Dremio Cloud\
**Created:** [March 26, 2025, 9:31am UTC](https://community.dremio.com/t/java-11-or-higher-is-required-to-run-dremio/12907 "2025-03-26T09:31:25Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![seetharam](https://avatars.discourse-cdn.com/v4/letter/s/ccd318/32.png) [@seetharam](https://community.dremio.com/u/seetharam)\
**Post date:** [March 26, 2025, 9:31am UTC](https://community.dremio.com/t/java-11-or-higher-is-required-to-run-dremio/12907/1 "2025-03-26T09:31:25Z")

</div>

Hi,

We are running dremio on docker hosts and trying upgarde dremio version to 25.2.1. and Mycoordinator container exited with the error.

““Java 11 or higher is required to run Dremio””

I have updated my docker base image to JDK 11 and JDK 17 still it throughs same error.

Regards  
Koya

---

<div class="post-metadata">

**Author:** ![balaji.ramaswamy](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/balaji.ramaswamy/32/843_2.png) [@balaji.ramaswamy](https://community.dremio.com/u/balaji.ramaswamy)\
**Post date:** [March 28, 2025, 5:32am UTC](https://community.dremio.com/t/java-11-or-higher-is-required-to-run-dremio/12907/2 "2025-03-28T05:32:55Z")

</div>

@seetharam The default home could still be pointing to JDK 8. Does Dremio 24.x start correctly? That should confirm if JDK is still pointing to 8

Maybe try this? `docker exec containerId java -version`

---

<div class="post-metadata">

**Author:** ![seetharam](https://avatars.discourse-cdn.com/v4/letter/s/ccd318/32.png) [@seetharam](https://community.dremio.com/u/seetharam)\
**Post date:** [April 2, 2025, 9:16am UTC](https://community.dremio.com/t/java-11-or-higher-is-required-to-run-dremio/12907/3 "2025-04-02T09:16:54Z")

</div>

On Master, I could see JDK version 17 but, executors are keep on restaring.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/dremio/original/2X/8/848fd889d34c294519d9fcc9a86a29810c08fc5f.png)

---

<div class="post-metadata">

**Author:** ![seetharam](https://avatars.discourse-cdn.com/v4/letter/s/ccd318/32.png) [@seetharam](https://community.dremio.com/u/seetharam)\
**Post date:** [April 2, 2025, 9:25am UTC](https://community.dremio.com/t/java-11-or-higher-is-required-to-run-dremio/12907/4 "2025-04-02T09:25:09Z")

</div>

During the Dremio version upgrade, I noticed `dremio-admin` files in `/opt/dremio/bin`. However, the upgrade process is still not completing successfully, and I’m encountering an issue where the KV store version is still uses the old version (24.0.0).

I tried to docker exec inside container to the 7opt/dremio/bin path to execute dremio-admin commands and faced dremio commnads not found.

- name: Upgrade dremio coordinator from {{fromVersion}} to {{image\_tag}}  
docker\_container:  
name: “dremio\_coord”  
image: “{{image}}:{{image\_tag}}”  
state: started  
entrypoint: [“/bin/bash”, “-c”]  
command: “/opt/dremio/bin/dremio-admin upgrade”  
#command: “/bin/bash -c ‘/opt/dremio/bin/dremio-admin upgrade; /opt/dremio/bin/dremio start-fg’”  
# entrypoint: “/bin/bash -c ’   
# /opt/dremio/bin/dremio-admin upgrade; \   
# /opt/dremio/bin/dremio start-fg’ "  
network\_mode: host  
hostname: ‘{{host\_name}}’  
# auto\_remove: True  
etc\_hosts: ‘{{hosts\_mapping}}’  
mounts:  
- { target: ‘/opt/dremio/data’, source: ‘{{local\_data\_store\_path}}/{{data\_volume}}’, type: ‘bind’ }  
#- { target: ‘/opt/dremio/keystore’, source: ‘{{local\_data\_store\_path}}/keystore’, type: ‘bind’ }  
- { target: ‘/opt/dremio/conf’, source: ‘{{config\_volume}}’ }  
- { target: ‘/opt/dremio/tls’, source: ‘{{tls\_volume}}’ }  
- { target: ‘/opt/dremio/log’, source: ‘{{log\_volume}}’ }  
- { target: ‘/mnt/cachemanagerdisk’, source: ‘{{local\_data\_store\_path}}/dremio-cache’, type: ‘bind’}  
env:  
DREMIO\_GC\_LOG\_TO\_CONSOLE: “yes”  
DREMIO\_MAX\_MEMORY\_SIZE\_MB: “{{DREMIO\_MAX\_MEMORY\_SIZE\_MB}}”  
DREMIO\_JAVA\_SERVER\_EXTRA\_OPTS: "  
-Dzookeeper={{zookeeperQ}}   
-Dservices.coordinator.enabled=true   
-Dservices.coordinator.master.enabled=true   
-Dservices.coordinator.master.embedded-zookeeper.enabled=false   
-Dservices.executor.enabled=false   
-Dregistration.publish-host={{host\_ip}}”