Reserved.

Hello @brody, the upcoming version 2.0.0 of Kuma Uptime updates the ping monitor to use a native/raw-socket. This doesn't seem to be supported on Railway at the moment as I am met with a spawn EPERM error whenever trying to add a ping monitor. Does Railway have plans to support this type of connection from a docker image in the future?

It will be supported by our VM runtime, which is still being developed internally, but it will not be supported on our current container-based runtime.

Does this template support IPv6? Trying to use it to monitor services on railway and the connection fails with
"connect ECONNREFUSED [ipv6 value]"