Repository navigation
Unable to open 'project': File is a directory. #374
Description
code-serverversion: codercom/code-server:latest- OS Version: Linux VM, Chrome 73.0.3683.86 (but also repro on Safari)
Description
Ever since yesterday anytime I run docker run -t -p 127.0.0.1:8443:8443 -v "$HOME/git/kaggleazure:/root/project" -v "/tmp/foobar:/root/.local" codercom/code-server:latest code-server --allow-http --no-auth (and pretty much any permutation of that) I'm not able to open a folder remotely (going to localhost:8443 on another machine that has port forward to the VM). The default working dir is set to /root/project/code-server for some reason. When I click Open Folder... the open file (yes, file, not sure why) dialog comes up . And when I click confirm at the directory I get the Unable to open 'project': File is a directory.. For some reason I'm stuck in a state where I can't open folders, no mater how many times I kill the image, use a different image, or clear local storage.
Activity
vimota commentedon Mar 29, 2019
The other weird thing is that this only happens on the remote machine, but if I access localhost:8443 on the Linux VM where code-server is running, I don't have that issue.
vimota commentedon Mar 29, 2019
Ah looks like this was the issue for me: 3b8cd0a#diff-04c6e90faac2675aa89e2176d2eec7d8 . When I change
code-server->.like so:docker run -t -p 127.0.0.1:8443:8443 -v "$HOME/git/kaggleazure:/root/project" -v "/tmp/foobar:/root/.local" codercom/code-server:latest . --allow-http --no-auth, the issue is resolved.vimota commentedon Mar 29, 2019
I'm not sure what that parameter is used for (the
code-serverone after the image name), or why this was causing different behaviour in remote and local client...Kiricon commentedon Apr 10, 2019
Having this exact same issue with a version of this code hosted on digital ocean. I can't open folders on my remote machine. 😢
Kiricon commentedon Apr 14, 2019
Just as an update: This issue seems to only happen I visit the page from a mac.