Networking Problem in Release Command

Hm… This part should be possible, at least, via the non-obvious --address flag. (And you can check the RELEASE_COMMAND environment variable once you’re in there, to verify.)

$ fly m list  # note IP ADDRESS
$ fly ssh console --address fdaa::<hex-digits>
# printenv RELEASE_COMMAND
1

Hope this helps a little!


Aside: There was a cluster of reports of the egress-ip feature failing recently. I wonder if you guys are all in the same region, :thought_balloon: