It appears that when I clone a machine into another region the FLY_IMAGE_REF gets messed up. As you can see from my config below the RELEASE_NODE format should be something like my-application-02JRWA8NR615ZWR4V3T2FV7E98@fdaa:15:a355:a8b:4b8:2f21:7ac0:1
but on the cloned machine I get the following error:
025-04-15T09:52:27.808 app[xyz] fra [info] Protocol 'inet6_tcp': invalid node name: my-application-02JRWA8NR615ZWR4V3T2FV7E98@sha256:c01ea8b8c711eda42f51a5773cdb6ca7f68e50879a820aebf24f82b434588502@fdaa:15:a355:a8b:4b8:2f21:7ac0:1
As you can see there are two @ signs in there and the sha256 (multihash prefix?) which breaks the node name assignment. Am I doing something wrong? Things work fine on the non-cloned machine.
#!/bin/sh
# configure node for distributed erlang with IPV6 support
export ERL_AFLAGS="-proto_dist inet6_tcp"
export ECTO_IPV6="true"
export DNS_CLUSTER_QUERY="${FLY_APP_NAME}.internal"
export RELEASE_DISTRIBUTION="name"
export RELEASE_NODE="${FLY_APP_NAME}-${FLY_IMAGE_REF##*-}@${FLY_PRIVATE_IP}"
# Uncomment to send crash dumps to stderr
# This can be useful for debugging, but may log sensitive information
# export ERL_CRASH_DUMP=/dev/stderr
# export ERL_CRASH_DUMP_BYTES=4096