Closed SeppiDamgaard closed 1 year ago
Hi, I published a pull request #22 to attempt to fix this issue. Please pull the latest image and see if it works for you now, and report back.
Unfortunately I am still getting the same error.
Just discovered a quick workaround for this, set the permissions on the host side to 1000:1000 as the container has a user 'terraria' using with 1000:1000 perms.
Should fix the issue of building the server.
Thanks for the information, @IAmChrisAMA . I will add this to the documentation.
Just discovered a quick workaround for this, set the permissions on the host side to 1000:1000 as the container has a user 'terraria' using with 1000:1000 perms.
Should fix the issue of building the server.
Hey how do I do this?
I fixed the issue, for me it had nothing to do with the image or container.
In unraid, if you haven't already, go to tools > New Permissions, select all disks and every share except appdata and run it.
Fixed this and boatload of other issues for me.
Please review the updated documentation covering some permission requirements on the host to support volume mapping.
It has been copied below for your reference. (Commit 95a967f)
Permission Configuration This container uses an account named terraria internally which is a low-privileged user. Due to Unix kernel constraints, it may be necessary to grant UID and GID 1000 access to the mapped world and mod directories to properly launch the server.
To do this easily, perform the following command on your HOST's Mod and World directories:
chown 1000:1000
Downloaded the container from the Unraid appstore, and I got some issues regarding the container seems to be missing access to files.
My other containers are working fine, and I've tried reinstalling this a couple of times.
The 'Worlds' and 'Workshop' folders are created like they should, but empty.
This is the error part of the console:
UnRaid Version: 6.11.3