v14 Stable Release

[felddy]

This container supports Foundry VTT stable release 14.359

See:

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

Warning

While this is categorized as a Stable release there is always a possibility of unexpected bugs or compatibility issues. As with any time you update the core software, be sure to perform a complete backup of your user data to minimize any risk of data loss.

Important Changes from v13

Primary registry is now GitHub Container Registry

Images are now published primarily to ghcr.io/felddy/foundryvtt. Stable releases continue to be mirrored to Docker Hub at docker.io/felddy/foundryvtt. All documentation and examples have been updated to use ghcr.io image references.

Platform support changes

• Dropped linux/arm/v7 support.
• Node.js upgraded from 22 to 24.
• Base image updated from Debian bookworm to Debian trixie.

New Foundry VTT configuration options

Several new options.json fields introduced in Foundry VTT Version 14 are now configurable via environment variable:

• FOUNDRY_CSS_THEME — Setup page theme. Default changed from foundry to dark to match Foundry's V14 default.
• FOUNDRY_DELETE_NEDB — Automatically delete legacy NeDB files after LevelDB migration.
• FOUNDRY_LOG_SIZE — Maximum log file size before rotation (e.g. 64m).
• FOUNDRY_MAX_LOGS — Maximum number of log files to retain.
• FOUNDRY_NO_BACKUPS — Disable automatic world backups before major version migrations.
• FOUNDRY_SERVICE_CONFIG — Path to a service configuration file.
• FOUNDRY_SERVICE_KEY — Service authentication key. May be set using secrets.
• FOUNDRY_TEMP_DIR — Temporary directory for package archive downloads, useful for hosts with constrained /data storage.
• FOUNDRY_UNIX_SOCKET — Unix domain socket path for the server listener.
• FOUNDRY_TELEMETRY — Fixed from string passthrough to proper boolean. It is recommended to explicitly set this to avoid a prompt on every container start.

Exponential backoff on container failure

The container now applies exponential backoff before exiting on any failure, protecting the Foundry API servers and your hosting environment from rapid restart loops. Previously, a misconfigured or crashing container could restart immediately and repeatedly — potentially hammering the Foundry download and license servers.

Supply chain security

Container images are now signed and published with verifiable SLSA Level 3 provenance, Software Bills of Materials (SBOMs), and vulnerability attestations via Trivy for every supported platform. These artifacts are attached to each image in the registry. The build pipeline has been upgraded to use felddy/reusable-workflows v4 with attestations: write permissions.

New Contributors

• @Taner314 made their first contribution in Add support for proxy in bootstrap scripts #1345

Full Changelog: v13.351.0...v14.359.0

---

This discussion was created from the release v14.359.0.

[alterNERDtive]

Huh, what does the FOUNDRY_SERVICE_* stuff do? I can’t seem to find anything in the Foundry docs for it.

[felddy]

Huh, what does the FOUNDRY_SERVICE_* stuff do? I can’t seem to find anything in the Foundry docs for it.

They are used to configure credentials for Foundry hosting providers. I'll clarify the docs next update.

[pittmanism]

Is it possible to run a module compatibility check with this somehow? I'd love to pull the next version, but I have no idea if my modules are supported yet or not. Am I missing something?

[felddy]

I've just update the compatibility check script for v14.360. See the discussion here:

• Check module compatibility at container startup: ✅⚠️🟠❌ #991