search

thomasfa18 / node-foundry

2 stars 2 forks source link

Issue upgrading or running a fresh install of 0.9.x #1

Closed TwilightDirge closed 2 years ago

TwilightDirge commented 2 years ago

Hi, Thanks for this container, it's been rock solid until now. If I upgrade to the stable 0.9.x version or try a fresh install of that version (which is the recommendation in the release notes (https://foundryvtt.com/releases/9.238) I get this error set and a rolling restart of the container.

2022-01-02 16:11:41 stdout (node:1) UnhandledPromiseRejectionWarning: Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only file and data URLs are supported by the default ESM loader 2022-01-02 16:11:42 stdout (node:1) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. 2022-01-02 16:11:42 stdout (node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 5) 2022-01-02 16:11:42 stdout (Use node --trace-warnings ... to show where the warning was created) 2022-01-02 16:11:42 stdout     at link (internal/modules/esm/module_job.js:41:36) 2022-01-02 16:11:42 stdout     at ModuleWrap. (internal/modules/esm/module_job.js:42:40) 2022-01-02 16:11:42 stdout     at Loader.getModuleJob (internal/modules/esm/loader.js:243:28) 2022-01-02 16:11:42 stdout     at Loader.resolve (internal/modules/esm/loader.js:97:40) 2022-01-02 16:11:42 stdout     at Loader.defaultResolve [as _resolve] (internal/modules/esm/resolve.js:720:11)

Any idea on how to fix it would be appreciated.

thomasfa18 commented 2 years ago

I'm away from desk at the moment can you please confirm if you have this issue after redeploying the container from a clean state or if you have this issue only after upgrading foundry within an existing container?

TwilightDirge commented 2 years ago

I've tried it both ways with the same results.

javelinfr commented 2 years ago

Hi, i have the same issue, updating or from fresh install (rolling restart of the container with the same error)

javelinfr commented 2 years ago

managed to get through it : recreating container with node:currentalpine3.15

thomasfa18 commented 2 years ago

managed to get through it : recreating container with node:currentalpine3.15

thanks for confirming. I've updated the dockerfile

thomasfa18 commented 2 years ago

new image pushed to docker repo with alpine 3.15 requirement