Startup Crash: uv_os_homedir returned ENOENT (no such file or directory)

[felddy]

Startup Crash: uv_os_homedir returned ENOENT (no such file or directory)

[TimPansino]

The offending line is an operating system call to os.homedir(). This is happening because I have the FOUNDRY_UID and FOUNDRY_GID env vars set. The entrypoint script does not create the user and group if they do not exist, causing this error.

[felddy]

Thanks for the report. I'm looking into it.

I set FOUNDRY_UID=1000 and FOUNDRY_GID=100 on my actual server and was not seeing this behavior:

...
foundry_1  | 'foundryvtt-0.6.4.zip' saved
foundry_1  | Installing Foundry Virtual Tabletop 0.6.4
foundry_1  | Switching uid:gid to 1000:100 and restarting.
foundry_1  | Starting felddy/foundryvtt container v0.6.4
foundry_1  | Foundry Virtual Tabletop 0.6.4 is installed.
foundry_1  | Generating options.json file.
foundry_1  | Setting 'Admin Access Key'.
foundry_1  | Starting Foundry Virtual Tabletop.
foundry_1  | FoundryVTT | 2020-06-23 15:19:45 | [info] Foundry Virtual Tabletop - Version 0.6.4
foundry_1  | FoundryVTT | 2020-06-23 15:19:45 | [info] Running on Node.js - Version 12.18.1
foundry_1  | FoundryVTT | 2020-06-23 15:19:45 | [info] Loading data from user directory - /data
foundry_1  | FoundryVTT | 2020-06-23 15:19:45 | [info] Application Options:
...

But I am able to reproduce it when I use FOUNDRY_UID=111 and FOUNDRY_GID=115: 🎉

...
foundry_1  | 'foundryvtt-0.6.4.zip' saved
foundry_1  | Installing Foundry Virtual Tabletop 0.6.4
foundry_1  | Applying license key.
foundry_1  | Switching uid:gid to 111:115 and restarting.
foundry_1  | Starting felddy/foundryvtt container v0.6.4
foundry_1  | Foundry Virtual Tabletop 0.6.4 is installed.
foundry_1  | Generating options.json file.
foundry_1  | Setting 'Admin Access Key'.
foundry_1  | Starting Foundry Virtual Tabletop.
foundry_1  | SystemError [ERR_SYSTEM_ERROR]: A system error occurred: uv_os_homedir returned ENOENT (no such file or directory)
foundry_1  |     at _getEnvDataPath (/home/foundry/resources/app/main.js:128:22)
foundry_1  |     at getPaths (/home/foundry/resources/app/main.js:55:23)
foundry_1  |     at Object.<anonymous> (/home/foundry/resources/app/main.js:158:18)
foundry_1  |     at Module._compile (internal/modules/cjs/loader.js:1138:30)
foundry_1  |     at Object.Module._extensions..js (internal/modules/cjs/loader.js:1158:10)
foundry_1  |     at Module.load (internal/modules/cjs/loader.js:986:32)
foundry_1  |     at Function.Module._load (internal/modules/cjs/loader.js:879:14)
foundry_1  |     at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:71:12)
foundry_1  |     at internal/main/run_main_module.js:17:47
...

Thanks again for reporting this. I'll get a fix for this up as soon as possible.

[felddy]

@TimPansino I just published v0.6.4+a

I believe that this will fixes the issue you reported. After updating I am no longer able to reproduce the error.

Please pull the new image from Docker hub, test, and let me know how it goes.

[felddy]

@TimPansino were you able to test the proposed fix?

[TimPansino]

I had not, I just tried with the latest build and that is working.

Unrelated but there's an issue with your CONTAINER_PATCHES logic. Seems you're testing a potentially unset variable for truth instead of testing if it's set. I can open a different issue for that though.

./entrypoint.sh: line 107: CONTAINER_PATCHES: parameter not set