This error occurs when I use arm64 server to run gate inside a k3s cluster inside oracle's vm.
Change Image to linux/arm64 version still happen.
After turn off bedrock it works without any errors.
2026-04-05T05:11:28.141Z INFO gate/root.go:144 starting Gate proxy {"version": "v0.64.0"}
2026-04-05T05:11:28.141Z INFO gate/root.go:145 logging verbosity {"verbosity": 0}
2026-04-05T05:11:28.141Z INFO gate/root.go:146 using config file {"config": "/config/config.yml"}
2026-04-05T05:11:28.141Z INFO config gate/gate.go:309 config validation warn {"warn": "bedrock: Floodgate key will be auto-generated in managed mode at \"floodgate.pem\""}
2026-04-05T05:11:28.157Z INFO config gate/gate.go:282 auto config reload enabled {"path": "/config/config.yml"}
2026-04-05T05:11:28.157Z INFO api api/server.go:34 starting api service {"bind": "0.0.0.0:8080"}
2026-04-05T05:11:28.157Z INFO java proxy/proxy.go:308 syncing servers... {"count": 1}
2026-04-05T05:11:28.157Z INFO bedrock geyser/geyser.go:58 bedrock config loaded {"floodgateKeyPath": "floodgate.pem", "geyserListenAddr": "localhost:25567", "usernameFormat": ".%s"}
2026-04-05T05:11:28.157Z INFO java proxy/proxy.go:492 registered new server {"name": "minecraft-server-service-lobby", "addr": "minecraft-server-service-lobby.minecraft-servers.svc.cluster.local:25565"}
2026-04-05T05:11:28.157Z INFO bedrock.managed managed/managed.go:590 generating floodgate key {"path": "floodgate.pem"}
2026-04-05T05:11:28.157Z INFO java proxy/proxy.go:373 registered builtin commands {"count": 3, "cmds": ["server", "glist", "send"]}
2026-04-05T05:11:28.157Z INFO java proxy/proxy.go:189 proxy protocol enabled
2026-04-05T05:11:28.157Z INFO bedrock.managed managed/managed.go:597 floodgate key generated successfully {"path": "floodgate.pem"}
2026-04-05T05:11:28.157Z INFO bedrock.geyser.managed managed/managed.go:54 ensuring geyser jar {"dataDir": ".geyser", "autoUpdate": true}
2026-04-05T05:11:28.158Z INFO java proxy/proxy.go:563 listening for connections {"addr": "0.0.0.0:25565"}
2026-04-05T05:11:28.158Z INFO bedrock.geyser.managed managed/managed.go:68 downloading geyser standalone (missing) {"url": "https://download.geysermc.org/v2/projects/geyser/versions/latest/builds/latest/downloads/standalone", "path": ".geyser/geyser-standalone.jar"}
2026-04-05T05:11:28.482Z INFO bedrock.geyser.managed managed/managed.go:72 geyser jar downloaded successfully{"path": ".geyser/geyser-standalone.jar"}
2026-04-05T05:11:28.483Z INFO bedrock.managed managed/managed.go:122 starting geyser standalone process {"java": "java", "jar": "/.geyser/geyser-standalone.jar", "config": "/.geyser/config.yml", "bedrockPort": 19132, "args": ["-jar", "/.geyser/geyser-standalone.jar", "--nogui", "--config", "/.geyser/config.yml"]}
2026-04-05T05:11:28.485Z ERROR bedrock proxy/proxy.go:80 failed to start geyser integration {"error": "managed geyser start failed: failed to start geyser process: fork/exec /opt/java/openjdk/bin/java: exec format error"}
go.minekube.com/gate/pkg/edition/bedrock/proxy.(*Proxy).Start
/workspace/pkg/edition/bedrock/proxy/proxy.go:80
go.minekube.com/gate/pkg/gate.New.func5
/workspace/pkg/gate/gate.go:110
go.minekube.com/gate/pkg/runtime/process.RunnableFunc.Start
/workspace/pkg/runtime/process/collection.go:33
go.minekube.com/gate/pkg/runtime/process.(*collection).startRunnable.func1
/workspace/pkg/runtime/process/internal.go:159
2026-04-05T05:11:28.485Z INFO java proxy/proxy.go:571 stopped listening for new connections {"addr": "0.0.0.0:25565"}
2026-04-05T05:11:28.485Z INFO java proxy/proxy.go:268 shutting down the proxy...
2026-04-05T05:11:28.485Z INFO java proxy/proxy.go:288 disconnecting all players... {"reason": "Server is restarting, please try again later."}
2026-04-05T05:11:28.485Z INFO api gate/api.go:61 api service stopped
2026-04-05T05:11:28.485Z INFO java proxy/proxy.go:291 disconnected all players. {"time": "800ns"}
2026-04-05T05:11:28.485Z INFO java proxy/proxy.go:293 waiting for all event handlers to complete...
2026-04-05T05:11:28.485Z INFO java proxy/proxy.go:271 finished shutdown. {"shutdownTime": "40µs", "totalTime": "328ms"}
error running Gate: managed geyser start failed: failed to start geyser process: fork/exec /opt/java/openjdk/bin/java: exec format error
This error occurs when I use arm64 server to run gate inside a k3s cluster inside oracle's vm.
Change Image to linux/arm64 version still happen.
After turn off bedrock it works without any errors.
System Arch : arrch64 (arm64)
K3s version : v1.34.6+k3s1
Containerd Version : containerd://2.2.2-bd1.34
System : Ubuntu 22.04.5 LTS
Kernal : 6.8.0-1044-oracle
Logs :