On 7/17/2025 at 10:30 AM, Squirreljester said:

I apologize, where do I find that?

In your unraid template, what is the text in the "Repository" field? The tag is what is after the colon.

On 7/18/2025 at 1:20 PM, voyager12 said:

In your unraid template, what is the text in the "Repository" field? The tag is what is after the colon.

dockerMan/templates-user.xml

<?xml version="1.0"?>

<Container version="2">

<Name>FoundryVTT</Name>

<Repository>felddy/foundryvtt:release</Repository>

<Registry>https://hub.docker.com/r/felddy/foundryvtt</Registry>

<Network>bridge</Network>

<MyIP/>

<Shell>sh</Shell>

<Privileged>false</Privileged>

<Support>https://forums.unraid.net/topic/121065-support-silman-foundryvtt-felddy-docker-image/</Support>

<Project>https://github.com/felddy/foundryvtt-docker</Project>

<Overview>A secure, reliable, compact, and simple-to-use container for the Foundry Virtual Tabletop using felddy's Dockerhub images.&#xD;

Felddy has the most robust docker image for FoundryVTT their image has over 10M downloads.&#xD;

&#xD;

You can get a Foundry Virtual Tabletop instance up and running in minutes using this container. This Docker container is designed to be secure, re

liable, compact, and simple to use. It only requires that you provide the credentials or URL needed to download a Foundry Virtual Tabletop distrib

ution.</Overview>

<Category>GameServers:</Category>

<WebUI>http://[IP]:[PORT:30000]</WebUI>

<TemplateURL>https://raw.githubusercontent.com/silman/unraid_templates/master/foundry/foundry.xml</TemplateURL>

<Icon>https://www.foundryvtt.wiki/fvtt-solid-512.png</Icon>

<ExtraParams/>

<PostArgs/>

<CPUset/>

<DateInstalled>1752594040</DateInstalled>

<DonateText/>

<DonateLink/>

<Requires/>

<Config Name="Game Data Path" Target="/data" Default="" Mode="rw" Description="Maps to container path /data. Path to persistent directory for st

oring Config, Data, and Logs directories for Foundry to use." Type="Path" Display="always" Required="true" Mask="false">/mnt/user/FoundryVTT/</Con

fig>

Anyone had issues with this docker image just failing to start, it seems to start for like a second and just stops.

On 7/18/2025 at 1:20 PM, voyager12 said:

In your unraid template, what is the text in the "Repository" field? The tag is what is after the colon.

Any ideas what's going on? I had this docker up and running for over 6 months without an issue, then I noticed it was off and wouldn't start.

I've even tried doing the extra parameters "--user 99:100" that I found earlier in the thread, but no luck.

What can I do?

I have a question on getting external folders from the share active from within foundry.

I created a specific share on the NVME that docker runs on for Foundry

Within that share I have the folder for foundry (modules, worlds, systems)

I also have a folder for assets.

I have the asset folder mounted as an additional path in the container config.

My rub is that I cant get the asset folder viewable from within the filepicker in foundry.

Is there a step that i'm missing? Im happy to provide other details as needed.

Does this container actually get fixes/updates regularly? I've noticed the icon for it has been broken for months now, and it still seems to have the same issue as a long time ago where it installs with incorrect permissions and so doesn't actually run without editing those...

Otherwise I'll try the other container that seems to have been released.

On 7/24/2025 at 7:34 PM, Squirreljester said:

Any ideas what's going on? I had this docker up and running for over 6 months without an issue, then I noticed it was off and wouldn't start.

I've even tried doing the extra parameters "--user 99:100" that I found earlier in the thread, but no luck.

What can I do?

So I think your

On 7/24/2025 at 7:34 PM, Squirreljester said:

Any ideas what's going on? I had this docker up and running for over 6 months without an issue, then I noticed it was off and wouldn't start.

I've even tried doing the extra parameters "--user 99:100" that I found earlier in the thread, but no luck.

What can I do?

So you've definitely updated to v13 which has the permission changes as mentioned in that link I sent a few comments back: https://github.com/felddy/foundryvtt-docker/releases/tag/v13.340.0. I would recommend pinning to a major version tag by setting repository field to felddy/foundryvtt:13 and keeping that last number to the major version you want to use. Changing that number is not backwards compatible so only do it intentionally. To get it to work with v13, you'll need to run chown -R 1000:1000 /mnt/user/<path_to_foundry_data_folder>. Or otherwise change the docker user container to match the data.

On 7/23/2025 at 5:18 PM, Inch said:

Anyone had issues with this docker image just failing to start, it seems to start for like a second and just stops.

Check the container logs. If I had to guess, you're having the same permission problems I just posted about. I would highly recommend people not using the release tag and using a tag of the major version they want to use otherwise you'll keep having problems similar to this with major releases without much warning when your container updates.

On 8/9/2025 at 1:56 PM, Nirin said:

Does this container actually get fixes/updates regularly? I've noticed the icon for it has been broken for months now, and it still seems to have the same issue as a long time ago where it installs with incorrect permissions and so doesn't actually run without editing those...

Otherwise I'll try the other container that seems to have been released.

It does but currently, container updates don't update your unRAID template which is the one that provides the image. I just updated the image url manually myself as the old one is no longer accessible and wasn't provided by the template owner anyways.

On 8/3/2025 at 10:35 AM, AndrewPr said:

I have a question on getting external folders from the share active from within foundry.

I created a specific share on the NVME that docker runs on for Foundry

Within that share I have the folder for foundry (modules, worlds, systems)

I also have a folder for assets.

I have the asset folder mounted as an additional path in the container config.

My rub is that I cant get the asset folder viewable from within the filepicker in foundry.

Is there a step that i'm missing? Im happy to provide other details as needed.

You'll need to provide more specific paths but just checking my installation, it looks like the top level folder that the file picker provides is the Data directory within the container path. So you'll need to make sure your asset folder is at a non-occupied location within /mnt/user/<foundry_folder>/Data/<unique_name>. This is called a recursive mount and is documented here: https://docs.docker.com/engine/storage/bind-mounts/#recursive-mounts. However, I do want to make one caveat if I can guess why you're trying to do this. If you're doing this because you want to share assets between different versions of foundry, then be cautious. Assets are not guaranteed to be backwards compatible between asset versions so if you create assets in v13 foundry in that folder and try to use it in a different instance of foundry (say in V12), you may run into compatibility issues. I originally thought I'd design my set up this way but ran into those issues. If you want to share assets between instances, it's usually more robust to just copy the data over manually from the Unraid command line, copying from older foundry version to newer, and allow the newer version to update the assets to be compatible with its version. That way they have separate copies and can edit them without issues.

On 8/10/2025 at 4:06 PM, voyager12 said:

So I think your

So you've definitely updated to v13 which has the permission changes as mentioned in that link I sent a few comments back: https://github.com/felddy/foundryvtt-docker/releases/tag/v13.340.0. I would recommend pinning to a major version tag by setting repository field to felddy/foundryvtt:13 and keeping that last number to the major version you want to use. Changing that number is not backwards compatible so only do it intentionally. To get it to work with v13, you'll need to run chown -R 1000:1000 /mnt/user/<path_to_foundry_data_folder>. Or otherwise change the docker user container to match the data.

I'm getting this at the end of the log and the container won't stay running:

Warning: Failed to open the file downloading.zip: Permission denied

* Failure writing output to destination

0 220M 0 1360 0 0 10249 0 6:16:41 --:--:-- 6:16:41 10225

* Connection #0 to host r2.foundryvtt.com left intact

curl: (23) Failure writing output to destination

Entrypoint | 2025-08-28 17:26:18 | [warn] Download from presigned URL failed with exit code 23.

Entrypoint | 2025-08-28 17:26:18 | [error] No valid cached release file found. Unable to proceed with installation.

36 minutes ago, Squirreljester said:

I'm getting this at the end of the log and the container won't stay running:

Warning: Failed to open the file downloading.zip: Permission denied

* Failure writing output to destination

0 220M 0 1360 0 0 10249 0 6:16:41 --:--:-- 6:16:41 10225

* Connection #0 to host r2.foundryvtt.com left intact

curl: (23) Failure writing output to destination

Entrypoint | 2025-08-28 17:26:18 | [warn] Download from presigned URL failed with exit code 23.

Entrypoint | 2025-08-28 17:26:18 | [error] No valid cached release file found. Unable to proceed with installation.

Definitely a file permissions issue. Google how to fix file permissions issues in Linux. I've already given you the command to use but it might be that the foundry user is a non-standard UID/GID.

14 hours ago, voyager12 said:

Definitely a file permissions issue. Google how to fix file permissions issues in Linux. I've already given you the command to use but it might be that the foundry user is a non-standard UID/GID.

I ran the chown -R 1000:1000 /mnt/user/FoundryVTT command already, and it didn't help, the docker still starts and then stops with the same error.

I also don't know what "change the docker user container to match the data." means. I've updated the docker settings with "--user 99:100" in the extra parameters and changes the repository to "felddy/foundryvtt:release" per your suggestions.

I'm not sure how to proceed to resolve this issue.

Having an issue with the license. No matter what I do, the container is refusing to accept any license put in the template or when I edit the .json file
FoundryVTT | 2026-06-16 19:07:15 | [error] Software license verification failed. Please confirm your Foundry Virtual Tabletop software license
There is also no screen on startup asking for the license key?