Check module v12
compatibility at container startup: ✅⚠️🟠❌
#991
Replies: 1 comment
-
I'm having some trouble getting this to work with 12.343.0; does this still work with v12+, or was this script v11 only? if I run a 13.344.0 image, configured the same way, I at least see a "Checking module compatibility with FoundryVTT" and "Installing semver package" log messages, but it doesn't provide any further log output. Setting CONTAINER_PATCH_URLS or CONTAINER_PATCHES doesn't seem to change log output for v12 whatsoever. I tried executing it directly and got this error over and over with different line numbers:
If I add
to the script, then run it, it seems to execute. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The container uses a startup flag called
--noupdate
that prevents updates from being applied through the GUI, and notifies the user topull
a new image. A side-effect of this is that the module compatibility checker in FoundryVTT11.315
is inaccessible, as it is tied to the update process.As a work-around I've created a container patch that will do a compatibility check when you startup the container.
You can have it run at container startup by adding the URL to the
CONTAINER_PATCH_URLS
environment variable:Warning
Only use patch URLs from trusted sources!
Note
Alternatively you can download the script and place in a directory inside your
data
mount. Then set theCONTAINER_PATCHES
environment variable to point to the directory. e.g.,CONTAINER_PATCHES=/data/container_patches
At startup you will now see output similar to this in the log:
This feature was requested by @cs96and, who also helped debug and improve it during development.
See:
Beta Was this translation helpful? Give feedback.
All reactions