ENOENT: no such file or directory, open '/null'

[libnine]

I'm struggling to debug my current code-server which I'm downloading in a Dockerfile found here: https://gist.github.com/libnine/641a5758b1d86b1b1d8a6012d692016e

Here are my logs from the container:

root@e77d166aebe8:/# code-server version
[2022-04-05T21:00:40.279Z] info  code-server 3.8.0 c4610f7829701aadb045d450013b84491c30580d
[2022-04-05T21:00:40.279Z] info  Using user-data-dir /home/ocm/.code-server/user
[2022-04-05T21:00:40.281Z] error ENOENT: no such file or directory, open '/null'

And my OS details:

Operating System: Ubuntu 20.04.4 LTS
Kernel: Linux 5.13.0-39-generic
Architecture: x86-64

Any help would be greatly appreciated!

[hello-smile6]

I'm struggling to debug my current code-server which I'm downloading in a Dockerfile found here: https://gist.github.com/libnine/641a5758b1d86b1b1d8a6012d692016e

Here are my logs from the container:

root@e77d166aebe8:/# code-server version
[2022-04-05T21:00:40.279Z] info  code-server 3.8.0 c4610f7829701aadb045d450013b84491c30580d
[2022-04-05T21:00:40.279Z] info  Using user-data-dir /home/ocm/.code-server/user
[2022-04-05T21:00:40.281Z] error ENOENT: no such file or directory, open '/null'

And my OS details:

Operating System: Ubuntu 20.04.4 LTS
Kernel: Linux 5.13.0-39-generic
Architecture: x86-64

Any help would be greatly appreciated!

What about mkdir /null?

[libnine]

I'm curious why a folder /null is required to begin with as I'd ideally like to avoid making one. Here's the logs though:

root@47b8efdd82de:/# mkdir /null
root@47b8efdd82de:/# code-server version
[2022-04-05T21:24:00.476Z] info  code-server 3.8.0 c4610f7829701aadb045d450013b84491c30580d
[2022-04-05T21:24:00.477Z] info  Using user-data-dir /home/ocm/.code-server/user
[2022-04-05T21:24:00.480Z] error EISDIR: illegal operation on a directory, read

[hello-smile6]

Strange. What if you add a user and try running code-server as a non-root user?

[libnine]

well... that seemed to do it:

matt@47b8efdd82de:~$ code-server version
[2022-04-05T21:29:34.480Z] info  Wrote default config file to ~/.config/code-server/config.yaml
[2022-04-05T21:29:34.738Z] info  code-server 3.8.0 c4610f7829701aadb045d450013b84491c30580d
[2022-04-05T21:29:34.739Z] info  Using user-data-dir ~/.local/share/code-server
[2022-04-05T21:29:34.747Z] info  Using config file ~/.config/code-server/config.yaml
[2022-04-05T21:29:34.747Z] info  HTTP server listening on http://127.0.0.1:8080 
[2022-04-05T21:29:34.747Z] info    - Authentication is enabled
[2022-04-05T21:29:34.747Z] info      - Using password from ~/.config/code-server/config.yaml
[2022-04-05T21:29:34.747Z] info    - Not serving HTTPS

[libnine]

any explanation as to why?

[hello-smile6]

any explanation as to why?

Many programs malfunction with root privileges. Maybe an environment variable was set to null for the root user, but not for other users. That would explain the ENOENT error and the /null access attempt. Also, code-server probably was actually attempting to write to a file, based on the EISDIR error.

[hello-smile6]

From comment:

What if you add a user and try running code-server as a non-root user?