Hey ~

i had an update yesterday and now find myself presented with the foundry page but no login prompt available. Can't get past it :s

that is not in my control at all, it is your browser.

Hello, I attempted to upgrade my FoundryVTT to 14 and now I am getting this error message.

node:internal/modules/cjs/loader:1459

throw err;

^

Error: Cannot find module '/foundry/fvtt/resources/app/main.js'

at Module._resolveFilename (node:internal/modules/cjs/loader:1456:15)

at defaultResolveImpl (node:internal/modules/cjs/loader:1066:19)

at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1071:22)

at Module._load (node:internal/modules/cjs/loader:1242:25)

at wrapModuleLoad (node:internal/modules/cjs/loader:255:19)

at Module.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:154:5)

at node:internal/main/run_main_module:33:47 {

code: 'MODULE_NOT_FOUND',

requireStack: []

}

Node.js v24.14.1

Since then I have uninstalled and reinstalled the container and copied the linux install to the /foundry/fvtt mapped directory and verified that it was there with ls but for whatever reason the container will not see the files.

root@Storage:/mnt/user/appdata/FoundryVTT# docker exec -it FoundryVTT bash

Storage:/# ls -la /foundry/fvtt/resources/app/

total 168

drwxrwxrw- 1 root root 224 May 29 04:00 .

drwxrwxrw- 1 root root 34 May 29 03:58 ..

drwxrwxrw- 1 root root 292 May 29 03:58 client

drwxrwxrw- 1 root root 254 May 29 03:58 common

drwxrwxrw- 1 root root 208 May 29 03:58 dist

-rwxrwxrw- 1 root root 7552 May 22 22:19 license.html

-rwxrwxrwx 1 root root 271 May 22 22:19 main.js

-rwxrwxrw- 1 root root 1212 May 22 22:19 main.mjs

drwxrwxrw- 1 root root 7434 May 29 03:58 node_modules

-rwxrwxrw- 1 root root 143772 May 22 22:19 package-lock.json

-rwxrwxrw- 1 root root 2841 May 22 22:19 package.json

drwxrwxrw- 1 root root 138 May 22 22:19 public

drwxrwxrw- 1 root root 244 May 29 04:00 templates

-rwxrwxrw- 1 root root 777 May 22 22:19 tsconfig.json

Storage:/# root@Storage:/mnt/user/appdata/FoundryVTT#

d4d94513a02e:/# cat /foundry/fvtt/resources/app/main.js

#!/usr/bin/env node

/**

* Bootstrap the Node.js loader to support ESM imports

* Required until https://github.com/electron/electron/issues/21457#issuecomment-815770296 is resolved

* @returns {Promise<void>}

*/

(async function() {

await import("./main.mjs");

})();

Edited May 29May 29 by BrunoVic

there is a problem in the version 14 update, i am working on it in my free time but i have not had much.

On 5/29/2026 at 9:37 AM, fithwum said:

there is a problem in the version 14 update, i am working on it in my free time but i have not had much.

Tried installing V14 on my server, but couldn't. Is there any ETA on the update for this fix ?

Edited June 2Jun 2 by Lancelotth

Can report that V14.364 appears to work. Just stopped the container, copied the linux files over to the appdata/FoundryVTT folder, and then started the container and got right in.

yes version 14 works.

Hi @fithwum , thank you very much for creating and maintaining this container. While developing some backup scripts for my Unraid server, I noticed that the container always takes 30 seconds to shut down. I am a docker novice so I used ChatGPT 5.6 to help investigate the problem. It came up with the diagnosis and solution below, which seems to work. Please accept my humble apologies for just pasting AI output here. I believe this may improve the package's shutdown behavior and I hope you will find it useful. Please do not feel any obligation to implement it, and thanks again for your work.

[This is ChatGPT speaking from here on] Hi — I wanted to report a small shutdown issue I found with the fithwum/foundry_vtt:alpine container.

The container starts with:

/bin/sh /ftemp/Install_Script.sh

and the script ultimately launches Foundry with:

su foundry -c 'node /foundry/fvtt/resources/app/main.js ...'

This leaves the shell as PID 1 and Node as a child. As a result, docker stop -t 30 FoundryVTT does not appear to deliver SIGTERM to Foundry. In my testing it waits the full 30 seconds and then exits with code 137, indicating Docker had to SIGKILL the container.

Sending SIGTERM directly to the Node process causes Foundry to shut down immediately and cleanly:

Shutting down Foundry Virtual Tabletop server
Shut-down success. Goodbye!

and the container exits with code 0.

One possible minimal fix, since this is an Alpine image, would be to use su-exec for the final privilege drop and exec, e.g.

exec su-exec foundry node /foundry/fvtt/resources/app/main.js --dataPath=/foundry/data --ignore-gpu-blacklist

with su-exec added to the image if it isn't already installed. That should leave Node as the container's main process after switching to the foundry user, allowing Docker's SIGTERM to reach Foundry normally.