# Latest docker image only shows JVM crash on Mac-M4

**URL:** <https://community.neo4j.com/t/latest-docker-image-only-shows-jvm-crash-on-mac-m4/72553>\
**Category:** Docker\
**Tags:** jvm\
**Created:** [February 6, 2025, 7:25pm UTC](https://community.neo4j.com/t/latest-docker-image-only-shows-jvm-crash-on-mac-m4/72553 "2025-02-06T19:25:52Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![tombrus](https://sea1.discourse-cdn.com/flex021/user_avatar/community.neo4j.com/tombrus/32/33973_2.png) [@tombrus](https://community.neo4j.com/u/tombrus)\
**Post date:** [February 6, 2025, 7:25pm UTC](https://community.neo4j.com/t/latest-docker-image-only-shows-jvm-crash-on-mac-m4/72553/1 "2025-02-06T19:25:52Z")

</div>

Hi community,

when I start the (now) [neo4j:latest docker image](https://hub.docker.com/layers/library/neo4j/latest/images/sha256-b9501881ef73cae2a5df25d60e61de067e9917ff8c7c0b797faf89e13f350666) I only see the following output:

```auto
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGILL (0x4) at pc=0x0000ffff9fd3fc5c, pid=95, tid=99
#
# JRE version: (21.0.6+7) (build )
# Java VM: OpenJDK 64-Bit Server VM (21.0.6+7-LTS, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-aarch64)
# Problematic frame:
# j java.lang.System.registerNatives()V+0 java.base@21.0.6
#
# No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /var/lib/neo4j/hs_err_pid95.log
[0.007s][warning][os] Loading hsdis library failed
#
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
/startup/docker-entrypoint.sh: line 300: 95 Aborted ${neo4j_admin_cmd} dbms set-initial-password "${password}" "${extra_args[@]}"

```

I am running docker on a **MacBookPro M4**.  
Previous version used to run fine (neo4j:5.26.2 and before).  
I noticed that the JDK version has been bumped from **JDK-17.0.14** to **JDK-21.0.6** so that might be related.

Any ideas how to avoid this?

Cheers,  
Tom