VSCode Desktop hangs after workspace update

Using VSCode on my Windows Desktop, conntected to Coder running on a Linux Docker. After a change in the Dockerfile of my rust environment in the Coder template, I am always unable to reconnect with VSC Desktop, after applying that update to the coresponding workspace. Failed to set up dynamic port forwarding connection over SSH to the VS Code Server. I don't really understand what this is supposed to tell me, since I didnt setup SSH with Coder, only HTTP(S). Is this a known issue or should i bring this to github? Current Workaround for me is to delete the Workspace and recreate it
13 Replies
Codercord
Codercord2mo ago
<#1305176078389739531>
Category
Bug report
Product
Coder OSS (v2)
Platform
Linux
Logs
Please post any relevant logs/error messages.
Phorcys
Phorcys2mo ago
hello @SpaceMoehre-i-nator™, you don't have to set up SSH for it to be active, Coder will encapsulate the SSH connection in whatever you're using to access the workspace (either DERP or HTTP(s)) the Coder VSCode ext uses SSH to take advantage of the existing "Remote - SSH" extension though this error is odd, could you send a screenshot of the workspace's page when this occurs? also, which version of Coder are you running?
SpaceMoehre-i-nator™
this was the output given in VSCode
Phorcys
Phorcys2mo ago
could you send this as well please? the workspace's page on the web ui
Phorcys
Phorcys2mo ago
is this while it doesn't work in VSCode?
SpaceMoehre-i-nator™
yes i replicated the error, confirmed the same error message and hit f5 in my browser after a bit of experimenting this seems to occure due to exchanging the image from "ubuntu:latest" -> "rust:latest", Dockerfile updates with the same image still work
Phorcys
Phorcys2mo ago
@SpaceMoehre-i-nator™ could you send a non-working version of your template so that I can try to reproduce?
SpaceMoehre-i-nator™
Changed this Dockerfile from ubuntu to rust:latest
FROM rust:latest

RUN apt-get update \
&& apt-get install -y \
curl \
git \
sudo \
vim \
wget \
cargo \
&& rm -rf /var/lib/apt/lists/*

ARG USER=coder
RUN useradd --groups sudo --no-create-home --shell /bin/bash ${USER} \
&& echo "${USER} ALL=(ALL) NOPASSWD:ALL" >/etc/sudoers.d/${USER} \
&& chmod 0440 /etc/sudoers.d/${USER}
USER ${USER}
WORKDIR /home/${USER}
FROM rust:latest

RUN apt-get update \
&& apt-get install -y \
curl \
git \
sudo \
vim \
wget \
cargo \
&& rm -rf /var/lib/apt/lists/*

ARG USER=coder
RUN useradd --groups sudo --no-create-home --shell /bin/bash ${USER} \
&& echo "${USER} ALL=(ALL) NOPASSWD:ALL" >/etc/sudoers.d/${USER} \
&& chmod 0440 /etc/sudoers.d/${USER}
USER ${USER}
WORKDIR /home/${USER}
Then published the template as active and updated the workspace
Phorcys
Phorcys3w ago
hey @SpaceMoehre-i-nator™ sorry for the delayed answer, I assume you've got this sorted out now?
SpaceMoehre-i-nator™
well i finished my template so it doesnt bother me anymore but i assume the bug still persists
Phorcys
Phorcys3w ago
oh yeah sorry didn't see

Did you find this page helpful?