Uderzo

Thanks for pointing that out, I hadn’t noticed the change. The template has been updated and should be working properly soon.

New version of Sharkord, support for PUID/PGID variables has been added.

The Sharkord Docker image no longer runs as root. It now runs as the non-root user “bun” (uid 1000). Because of this, the container no longer uses /root/.config/sharkord for its data. It now uses /home/bun/.config/sharkord instead. The template has been updated to reflect this change. If you were using the old template, Sharkord may have appeared to reset or show permission errors because it could not access the old root-based path. If you used the old template, edit your container and change the container path from /root/.config/sharkord to /home/bun/.config/sharkord, then apply the changes so the container is recreated. After that, run the following on Unraid to fix permissions if you get EACCES errors: chown -R 1000:1000 /mnt/user/appdata/sharkord Then restart the container.

Sharkord template has been updated The WebRTC port range is no longer required. Only port 40000 (TCP and UDP) is needed. You can either: Delete the container template and re-add it to use the updated version, or Manually change the WebRTC port from 40000-40020 to 40000 (TCP and UDP). You can change the WebRTC port in: /appdata/sharkord/config.ini [webRtc] port=40000 If you change this value, the port must match the TCP and UDP port configured in the Unraid template.

This is a support thread for this repo: https://github.com/BabaBooey84/unraid-templates I'm maintaining the templates for the community.

Check the RAM using memtest. I struggled with instability like this, and it was faulty RAM.

The latest update caused the docker container to stop running. I assume this is due to the recent changes mentioned above. How can I fix this?