Latest Flyway image crashes on M4 Max Apple Macbook pro #78
Description
The latest flyway image with the following hash: sha256:3d53fbf49bbe930d014e50330ea4dd26b1ba568a2f4f62f1d008b044714af2c9 crashes on M4 Max Apple Macbook pro when run.
The tags that were being used were: flyway/flyway:11-alpine
The logs are as follows:
2025-02-07 11:00:38 # A fatal error has been detected by the Java Runtime Environment:
2025-02-07 11:00:38 #
2025-02-07 11:00:38 # SIGILL (0x4) at pc=0x0000ffffa273fc5c, pid=10, tid=11
2025-02-07 11:00:38 #
2025-02-07 11:00:38 # JRE version: (21.0.6+7) (build )
2025-02-07 11:00:38 # 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)
2025-02-07 11:00:38 # Problematic frame:
2025-02-07 11:00:38 # j java.lang.System.registerNatives()V+0 java.base@21.0.6
2025-02-07 11:00:38 #
2025-02-07 11:00:38 # No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
2025-02-07 11:00:38 #
2025-02-07 11:00:38 # An error report file with more information is saved as:
2025-02-07 11:00:38 # /flyway/hs_err_pid10.log
2025-02-07 11:00:38 [0.021s][warning][os] Loading hsdis library failed
2025-02-07 11:00:38 #
2025-02-07 11:00:38 # The crash happened outside the Java Virtual Machine in native code.
2025-02-07 11:00:38 # See problematic frame for where to report the bug.
2025-02-07 11:00:38 #
2025-02-07 11:00:38 /flyway/flyway: line 41: 10 Aborted "$JAVA_CMD" $JAVA_ARGS "$EXTRA_ARGS" -cp "$CP" org.flywaydb.commandline.Main "$@"
Other posts from other developers regarding this issue: