truenas

[eunaotenhoid]

Feature description

Hi man? everything ok? could you add installation support for truenas?

ty for work

Motivation

I don't know

Example

I don't know

Pitch

I don't know

Code of Conduct

• I agree to follow this project's Code of Conduct

[felddy]

I don't know.

[gajustempus]

I'm running FoundryVTT on TrueNAS Scale at the moment. Works fine, but you have to click on "Custom App" when you're in the App catalogue.

settings I use:
Image

• felddy/foundryvtt
  Tag
• release
  Pull Policy
• Pull the image if it is not already present on the host

Environment Variables (add these)

• FOUNDRY_PASSWORD
• Value: YourFoundryVTTPassword
• FOUNDRY_USERNAME
• Value: YourFoundryVTTUsername
• FOUNDRY_ADMIN_KEY
• YourFoundryAdminPassword

Restart Policy

• Unless Stopped

Ports

• Container-Port: 30000
• Host Port: 30000
• Protocol: TCP

Portal Configuration

• Name: Web UI
• Protocol: HTTP
• Port: 30000
• Path: /

Storage Configuration

• Type: ixVolume (Dataset created automatically by the system)
• Mount Path: /data
• Dataset Name: storage_entry

with these settings in place, my Foundry works fine and the files are persistent.

[eunaotenhoid]

• storage_entry

I have no words to express my gratitude, THANK YOU SO MUCH!

Just out of curiosity about custom app, how do I add an image to represent the foundry in truenas?

[gajustempus]

THAT is a matter several people discuss. However it seems like you'd have to customize on TrueNAS itself via SSH/Terminal access. If you want to go that extra mile, it's being discussed here:

https://forums.truenas.com/t/how-to-change-icon-of-custom-app/24789/18

[github-actions]

This issue has been automatically marked as stale because it has been inactive for 28 days. To reactivate the issue, simply post a comment with the requested information to help us diagnose this issue. If this issue remains inactive for another 7 days, it will be automatically closed.

[AgentCrowe]

Hello!

I have been running this for a few weeks now without issue. However my TrueNas server rebooted and now the docker image just crashes everytime it loads. I have had to work through a few issues Usually the error message is pretty easy to figure out but I am not sure what its trying to tell me here. If anyone can point a direction to start that would be hugely helpful

[AgentCrowe]

Error: ENOENT: no such file or directory, open '/home/foundry/resources/app/public/lang/en.json'
at Object.openSync (node:fs:596:3)
at readFileSync (node:fs:464:35)
at file:///home/foundry/patch_lang.js:4:23
at ModuleJob.run (node:internal/modules/esm/module_job:195:25)
at async ModuleLoader.import (node:internal/modules/esm/loader:337:24)
at async loadESM (node:internal/process/esm_loader:34:7)
at async handleMainPromise (node:internal/modules/run_main:106:12) {
errno: -2,
syscall: 'open',
code: 'ENOENT',
path: '/home/foundry/resources/app/public/lang/en.json'

This is the more specific error message. Pull from docker logs.

Hello!

I have been running this for a few weeks now without issue. However my TrueNas server rebooted and now the docker image just crashes everytime it loads. I have had to work through a few issues Usually the error message is pretty easy to figure out but I am not sure what its trying to tell me here. If anyone can point a direction to start that would be hugely helpful

[gajustempus]

Hello!

I have been running this for a few weeks now without issue. However my TrueNas server rebooted and now the docker image just crashes everytime it loads.

I think your TrueNAS pulled the newst image - and the more recent one doesn't run under root anymore, requires the proper rights to access its data folder.

Head over to the TrueNAS Shell and type:

sudo chown 1000:1000 /mnt/.ix-apps/app_mounts/foundry/storage_entry

then re-run the container. That should fix the issue