Azure/Bridge-To-Kubernetes

Failed to Launch endpointmanager - /dev/tty No Such device or address

hsubramanianaks opened this issue · 0 comments

Describe the bug
Failed to Launch endpointmanager - /dev/tty No Such device or address

Mention the platform you are using
Linux/Ubuntu/Debian

To Reproduce
Steps to reproduce the behavior:
Debug using Bridge vscode extension

Expected behavior
Should launch endpointmanager without issues

Logs:

2023-09-21T07:32:36.8491570Z | Library | TRACE | Launch EndpointManager: pkexec env HOME="/home/azuretester/" bash -c "\"/home/azuretester/.config/Code/User/globalStorage/mindaro.mindaro/file-downloader-downloads/bridge/EndpointManager/EndpointManager\" \"azuretester\" \"/home/azuretester/.bridge/EndpointManager/EndpointManagerSocket\" \"/tmp/Bridge To Kubernetes\" \"5c15b3ad-767d-4c89-9e86-7a5fdc25d6751695281330503:3b365db07195:b0d47f50aab9:101fd79a0377\" &> /dev/null &"
2023-09-21T07:32:36.8496842Z | Library | TRACE | Setting the 'DOTNET_ROOT' environment variable with '/home/azuretester/.config/Code/User/globalStorage/mindaro.mindaro/file-downloader-downloads/dotnet' while launching 'EndpointManager'.
2023-09-21T07:32:36.8553423Z | Library | TRACE | Launch output: Waiting for process 12471
2023-09-21T07:32:36.8724716Z | Library | TRACE | Launch output: Error creating textual authentication agent: Error opening current controlling terminal for the process (`/dev/tty'): No such device or address
2023-09-21T07:32:36.8738272Z | Library | TRACE | Launch
 output: Process has exited with exit code 127

Additional context
Add any other context about the problem here.