v13.340.0

[felddy]

This pre-release container supports Foundry VTT testing release 13.340

See:

• https://foundryvtt.com/releases/13.340

Warning

This Testing update is intended for those dedicated users who wish to test the new features provided in Version 13. It is not intended for use in weekly games or in games with heavy use of add-on modules. The goal for this build is to collect preliminary testing feedback from developers and users, not to power actual game sessions!

Important Changes from v12

There were substantial internal changes introduced at release v13.333.0 that may affect some users:

• The container now defaults to a non-root user.
• The internal home directory has changed from /home/foundry to /home/node
• FOUNDRY_UID and FOUNDRY_GID environment variables have been deprecated.
  The Docker user option should be used to change the uid and gid of the running processes.
• The container will no longer change the permissions in the data volume to match the uid and gid of the server. Therefore the CONTAINER_PRESERVE_OWNER environment variable is deprecated.
• The TIMEZONE environment variable has been replaced by the standard TZ environment variable.

What's Changed

• Bump crazy-max/ghaction-github-labeler from 5.2.0 to 5.3.0 in the github-actions-all group by @dependabot in Bump crazy-max/ghaction-github-labeler from 5.2.0 to 5.3.0 in the github-actions-all group #1190
• Bump the github-actions-all group with 2 updates by @dependabot in Bump the github-actions-all group with 2 updates #1191
• Bump typescript from 5.8.2 to 5.8.3 in the npm-all group by @dependabot in Bump typescript from 5.8.2 to 5.8.3 in the npm-all group #1192
• Bump github/codeql-action from 3.28.13 to 3.28.15 in the github-actions-all group by @dependabot in Bump github/codeql-action from 3.28.13 to 3.28.15 in the github-actions-all group #1194
• Prerelease 13.340.0 by @felddy in Prerelease 13.340.0 #1195

Full Changelog: v13.339.0...v13.340.0

---

This discussion was created from the release v13.340.0.

[HumanWreck]

Hello @felddy,

thank you for all your work, my little DnD group is really enjoying playing on our own synology NAS. I am a very basic user, though, and encountered some problems when moving to 13.xxx. I would like to kindly ask you for an advice.

If I keep /home/node as internal directory when setting up the container, the game starts, but I don´t see any of my worlds, like it is a fresh install. If I manually change it back to /home/foundry (which I probably shouldn´t do) the container stops working immediately. I used the new node.js version from FVTT page (tried both with cache and URL). Could you please describe me a little bit how this "internal home directory" thing work and what changes should I do with this kind of a different update? I even tried, with no success, renaming my Foundry folder to "node" which is probably insane and laughable, but I was really desperate. Thank you, I am your big fan.

NAS: DS 220+
Container management: Container Manager, 24.0.2-1535
FVTT: 12.331 -> 13

[felddy]

Unless you're creating your own derivative image you should not be attempting to change the internals of the container. Make sure that you have the latest v13 image pulled down. When you start it up check the logs for errors.

Head over to this thread to diagnose any issues you see in the v13 container:

• `v13` Breaking Changes and Fixes #1197

[HumanWreck]

Thank you very much, problem solved!