-
Notifications
You must be signed in to change notification settings - Fork 892
Coder CLI is not in the $PATH
on Windows workspaces
#4870
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
The coder CLI is installed since it functions as the workspace agent, but it looks like it's not added to the PATH correctly. Adding directories to PATH in Windows sucks big time, so I expect this to not work in terminals made by the RDP session, but it should at least work over SSH or in the web terminal since we control the environment for those. |
Could we not put the coder binary somewhere that is most commonly included in the Windows PATH? |
This issue is becoming stale. In order to keep the tracker readable and actionable, I'm going close to this issue in 7 days if there isn't more activity. |
I'm also having this issue with the PATH. For anyone else who encounters this, the default path you can add to PATH manually is |
$PATH
on Windows workspaces
I believe this is fixed. |
Uh oh!
There was an error while loading. Please reload this page.
After provisioning a windows workspace using our templates the
coder
binary is not installed.Whereas when provisioning a linux and macos workspace using our templates the
coder
binary is installed.question: seeking confirmation that the
coder
CLI should be installed by default and on the path (ie via fetching /bin)ps. Here is my template -> https://gist.github.com/ghuntley/1ca092e4433175a596b387a7b5e4b613
The text was updated successfully, but these errors were encountered: