Looks right. I’d simplify the vm.args just in case though, you don’t need any of that, the taurus script generated by rebar3/relx will handle everything if you set ERL_DIST_PORT.
But note you can’t do this with -env ERL_DIST_PORT 4369 since that is an arg to Erlang VM and thus won’t be picked up by the shell script taurus. Since you are using Docker you’ll want to set it in the Dockerfile or with -e or under environment if using docker compose.
@tsloughter That’s correct. I’ve set ERL_DIST_PORT in my Dockerfile to make things as described in your post. But i’m still unable to connect to my node using remote_console
@tsloughter not publicly accessible unfortunately. Just for me to understand: in your case, you disabled epmd and were able to remote_console into the node inside Docker?
If yes, I must be doing something wrong.
@tsloughter it seems that erl_call can’t connect to my node.
$ echo $ERL_DIST_PORT
4369
$ /bin/sh -x /opt/taurus/bin/taurus remote_console
[...]
/opt/taurus/erts-14.1.1/bin/erl_call -R -c awesome_cookie -address 4369 -timeout 60 -a erlang is_alive
erl_call: failed to connect to node with address ":4369"
+ result=
+ code=1
+ [ 1 -eq 0 ]
+ return 1
+ echo Node is not running!
Node is not running!
$ ss -antp | grep 4369
$
This is strange. If i deploy my app outside the container, the above steps worked as expected and I can remote_console. But from within the Docker container, my release isn’t listening on port 4369.
