/opt/eturnal/erts-15.1.2/bin/erlexec: not found

[FarisZR]

Hi im facing this issue when starting eturnal with v1.12.0 and edge.

v1.12.2 image logs

eturnal-1  | run.sh: Start init script ...
eturnal-1  | run.sh: Container runs eturnal vsn 1.12.0+62 ...
eturnal-1  | run.sh: Documentation on https://eturnal.net ...
eturnal-1  | run.sh: Source code on https://github.com/processone/eturnal ...
eturnal-1  | run.sh: Read secrets defined as "Docker secrets" - if any ...
eturnal-1  | /usr/local/bin/eturnalctl: line 5: stun: not found
eturnal-1  | /usr/local/bin/eturnalctl: line 6: stun: not found
eturnal-1  | Exec: /opt/eturnal/erts-15.1.2/bin/erlexec -noinput +Bd -boot /opt/eturnal/releases/1.12.0+62/start -mode embedded -boot_var SYSTEM_LIB_DIR /opt/eturnal/lib -config /opt/eturnal/releases/1.12.0+62/sys.config -args_file /opt/eturnal/releases/1.12.0+62/vm.args -erl_epmd_port 3470 -start_epmd false -- foreground
eturnal-1  | Root: /opt/eturnal
eturnal-1  | /opt/eturnal
eturnal-1  | /opt/eturnal/bin/eturnal: exec: line 1011: /opt/eturnal/erts-15.1.2/bin/erlexec: not found

v1.11.0 logs

eturnal-1  | Exec: /opt/eturnal/erts-15.1.2/bin/erlexec -noinput +Bd -boot /opt/eturnal/releases/1.12.0+62/start -mode embedded -boot_var SYSTEM_LIB_DIR /opt/eturnal/lib -config /opt/eturnal/releases/1.12.0+62/sys.config -args_file /opt/eturnal/releases/1.12.0+62/vm.args -erl_epmd_port 3470 -start_epmd false -- foreground
eturnal-1  | Root: /opt/eturnal
eturnal-1  | /opt/eturnal

setup details

https://github.com/aosus/cups-g11/blob/677398e07604f4d3a4008f8b21fb52b348223b3e/matrix/docker-compose.yml#L114

[FarisZR]

the v1.12.1 image seems to still work, even though the vsn is showing the same version 1.12.0+62

eturnal-1  | run.sh: Start init script ...
eturnal-1  | run.sh: Container runs eturnal vsn 1.12.0+62 ...
eturnal-1  | run.sh: Documentation on https://eturnal.net ...
eturnal-1  | run.sh: Source code on https://github.com/processone/eturnal ...
eturnal-1  | run.sh: Read secrets defined as "Docker secrets" - if any ...
eturnal-1  | Exec: /opt/eturnal/erts-15.1.2/bin/erlexec -noinput +Bd -boot /opt/eturnal/releases/1.12.0+62/start -mode embedded -boot_var SYSTEM_LIB_DIR /opt/eturnal/lib -config /opt/eturnal/releases/1.12.0+62/sys.config -args_file /opt/eturnal/releases/1.12.0+62/vm.args -erl_epmd_port 3470 -start_epmd false -- foreground
eturnal-1  | Root: /opt/eturnal
eturnal-1  | /opt/eturnal

[sando38]

For me it starts fine:

:~$ docker run --rm ghcr.io/processone/eturnal:edge
Unable to find image 'ghcr.io/processone/eturnal:edge' locally
edge: Pulling from processone/eturnal
ff83864fa762: Pull complete
3d6594c59a64: Pull complete
eeef450e511e: Pull complete
4f4fb700ef54: Pull complete
Digest: sha256:c8fdc2e8077af6b61e3d46701b627934b115f73fcf45c1860e6b9b848c405e50
Status: Downloaded newer image for ghcr.io/processone/eturnal:edge
run.sh: Start init script ...
run.sh: Container runs eturnal vsn 1.12.2+3 ...
run.sh: Documentation on https://eturnal.net ...
run.sh: Source code on https://github.com/processone/eturnal ...
run.sh: Read secrets defined as "Docker secrets" - if any ...
Cannot query stun.conversations.im:3478: non-existing domain
Exec: /opt/eturnal/erts-15.2.6/bin/erlexec -noinput +Bd -boot /opt/eturnal/releases/1.12.2+3/start -mode embedded -boot_var SYSTEM_LIB_DIR /opt/eturnal/lib -config /opt/eturnal/releases/1.12.2+3/sys.config -args_file /opt/eturnal/releases/1.12.2+3/vm.args -erl_epmd_port 3470 -start_epmd false -- foreground
Root: /opt/eturnal
/opt/eturnal
2025-07-26 06:46:54.457874+00:00 [notice] Starting eturnal 1.12.2+3 on Erlang/OTP 27 (ERTS 15.2.6)
2025-07-26 06:46:54.458018+00:00 [info] Got no NOTIFY_SOCKET, notifications disabled
2025-07-26 06:46:54.458072+00:00 [info] Relay IPv4 address: 194.32.120.113 (port range: 49152-65535)
2025-07-26 06:46:54.458131+00:00 [info] Relay IPv6 address not configured
2025-07-26 06:46:54.458183+00:00 [info] Listening on 127.0.0.1:3470 (tcp) (Erlang protocol version 5)
2025-07-26 06:46:54.458388+00:00 [info] Started mod_log_stun
2025-07-26 06:46:54.458905+00:00 [info] Listening on [::]:3478 (udp) (STUN/TURN)
2025-07-26 06:46:54.459402+00:00 [info] Listening on [::]:3478 (tcp) (STUN/TURN)

also it shows the "correct" version. Are you running x86 or arm? Although I believe that should not be an issue here.

[FarisZR]

X86

[sando38]

X86

$ docker run --rm ghcr.io/processone/eturnal:edge@sha256:c8fdc2e8077af6b61e3d46701b627934b115f73fcf45c1860e6b9b848c405e50
run.sh: Start init script ...
run.sh: Container runs eturnal vsn 1.12.2+3 ...
run.sh: Documentation on https://eturnal.net ...
run.sh: Source code on https://github.com/processone/eturnal ...
run.sh: Read secrets defined as "Docker secrets" - if any ...
Cannot query stun.conversations.im:3478: non-existing domain
Exec: /opt/eturnal/erts-15.2.6/bin/erlexec -noinput +Bd -boot /opt/eturnal/releases/1.12.2+3/start -mode embedded -boot_var SYSTEM_LIB_DIR /opt/eturnal/lib -config /opt/eturnal/releases/1.12.2+3/sys.config -args_file /opt/eturnal/releases/1.12.2+3/vm.args -erl_epmd_port 3470 -start_epmd false -- foreground
Root: /opt/eturnal
/opt/eturnal
2025-08-04 05:54:40.574735+00:00 [notice] Starting eturnal 1.12.2+3 on Erlang/OTP 27 (ERTS 15.2.6)
2025-08-04 05:54:40.574889+00:00 [info] Got no NOTIFY_SOCKET, notifications disabled
2025-08-04 05:54:40.574946+00:00 [info] Relay IPv4 address: 194.32.120.113 (port range: 49152-65535)
2025-08-04 05:54:40.574984+00:00 [info] Relay IPv6 address not configured
2025-08-04 05:54:40.575031+00:00 [info] Listening on 127.0.0.1:3470 (tcp) (Erlang protocol version 5)
2025-08-04 05:54:40.575372+00:00 [info] Started mod_log_stun
2025-08-04 05:54:40.575817+00:00 [info] Listening on [::]:3478 (udp) (STUN/TURN)
2025-08-04 05:54:40.576143+00:00 [info] Listening on [::]:3478 (tcp) (STUN/TURN)

I run x86 as well, using the exact same image has as you linked to. above are my results. Maybe your docker has "cached" an old image or you need to run docker compose down and docker compose up again?

[BVollmerhaus]

If I recall correctly, I had a similar issue after updating an existing Compose service from 1.12.1 to 1.12.2.

Could you try to delete the anonymous volume that the eturnal image creates? I think that resolved it for me.

[sando38]

Could you try to delete the anonymous volume that the eturnal image creates? I think that resolved it for me.

Thanks for that hint. Will check that on my end as well and see if a fix to the Dockerfile is needed.