Error when using action-upterm, Error: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial unix /home/runner/.upterm/*.sock: connect: no such file or directory"

[tom-quiltt]

Error when using lhotari/action-upterm, was working yesterday, not sure what went wrong.

Run lhotari/action-upterm@v1
upterm

Auto-generating ~/.ssh/known_hosts by attempting connection to uptermd.upterm.dev
Pseudo-terminal will not be allocated because stdin is not a terminal.

ssh: connect to host uptermd.upterm.dev port 22: Network is unreachable

Creating a new session. Connecting to upterm server ssh://uptermd.upterm.dev:22
Created new session successfully
Entering main loop
Error: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial unix /home/runner/.upterm/*.sock: connect: no such file or directory"

Usage:
  upterm session current [flags]

Aliases:
  current, c

Examples:
  # Display the current session defined in $UPTERM_ADMIN_SOCKET
  upterm session current
  # Display the current session with a custom path
  upterm session current --admin-socket ADMIN_SOCKET_PATH

Flags:
      --admin-socket string   admin unix domain socket (required)
  -h, --help                  help for current

time="[20](https://github.com/quiltt/quiltt/actions/runs/3064324589/jobs/4947319032#step:6:21)[22](https://github.com/quiltt/quiltt/actions/runs/3064324589/jobs/4947319032#step:6:23)-09-15T[23](https://github.com/quiltt/quiltt/actions/runs/3064324589/jobs/4947319032#step:6:24):[20](https://github.com/quiltt/quiltt/actions/runs/3064324589/jobs/4947319032#step:6:21):01Z" level=fatal msg="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /home/runner/.upterm/*.sock: connect: no such file or directory\""

1

[JudeaDumont]

I am experiencing the same issue

[joebell1329]

Same issue here. Did you ever resolve it?

[Trass3r]

Occurred for me when running the job in a container.

[mmcky]

I am getting this issue as well -- running inside of a Docker container seems problematic.