Skip to content
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

Error: ENOENT: no such file or directory, open '/root/.code-server/globalStorage/state.json' #116

Closed
gerroon opened this issue Mar 8, 2019 · 5 comments
Labels
bug Something isn't working

Comments

@gerroon
Copy link

gerroon commented Mar 8, 2019

Debian Buster x64, using Docker

docker run -p 4141:8443 -v /media/codeserver:/root/project codercom/code-server code-server --allow-http --no-auth

INFO  WebSocket opened / {"client":1,"ip":"192.168.1.10"}
INFO  Created data directory
INFO  WebSocket closed / {"client":1,"code":1001}
INFO  WebSocket opened / {"client":2,"ip":"192.168.1.10"}
INFO  Created data directory
INFO  WebSocket closed / {"client":2,"code":1001}
INFO  WebSocket opened / {"client":3,"ip":"192.168.1.10"}
INFO  Created data directory
INFO  WebSocket closed / {"client":3,"code":1006}
fs.js:646
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
                 ^

Error: ENOENT: no such file or directory, open '/root/.code-server/globalStorage/state.json'
    at Object.fs.openSync (fs.js:646:18)
    at Object.fs.writeFileSync (fs.js:1299:33)
    at IncomingMessage.e.on (/usr/local/bin/code-server:557:107020)
    at emitNone (events.js:106:13)
    at IncomingMessage.emit (events.js:208:7)
    at endReadableNT (_stream_readable.js:1064:12)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
@kylecarbs
Copy link
Member

Interesting. What if you create that file?

@kylecarbs kylecarbs added the bug Something isn't working label Mar 8, 2019
@gerroon
Copy link
Author

gerroon commented Mar 8, 2019

In the docker image? That is right out of the recommended Docker image. I have not touched it myself.

@code-asher
Copy link
Member

Probably fixed by e597d49#diff-c3ab4160f569d8f1ba53d30b968e9f04R262, caused when unloading the page triggers a save for the settings but the directory hasn't been created yet (or has been deleted).

@nol166
Copy link
Contributor

nol166 commented Mar 12, 2019

@coderasher I restarted the docker command and it seemed to run without crashing the second time

@code-asher
Copy link
Member

Latest release should fix this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants