Repository navigation
Shoko #2135
Description
Activity
The Shoko script is ready for testing:
bash -c "$(curl -fsSL https://github.com/community-scripts/ProxmoxVED/raw/main/ct/shoko.sh)"Complete the first-run wizard at http://:8111. An AniDB account is required - Shoko identifies files against AniDB and without it the whole point is lost.
AniDB enforces strict rate limits and bans clients that hammer the API. Leave the default throttling alone when importing a large collection, or the account gets temporarily banned.
Your anime files are not stored in the container - mount the library into the LXC and add it as an import folder. Shoko's own database and settings live in /opt/shoko_data.
Runs on the framework-dependent release build with the ASP.NET Core 8 runtime from Debian, so no .NET SDK and no compilation is needed. Upstream also documents a source build, which this script does not use.Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.
Discord testing thread: https://discord.com/channels/1302816934508630047/1534106619393347594
- added a commit that references this issue
on Aug 12, 2026 When I tried to rename and move files through shoko, I kept on getting permission errors. The lxc is running unprivileged and the library is mounted in the lxc. I tried manually creating a test directory and I am getting a permission denied. Below is the perms on the directory inside the shoko lxc.
root@shoko:/media# ls -al anime/ total 66 drwxrwsr-x 4 nobody nogroup 4 Sep 7 2025 . drwxr-xr-x 9 nobody nogroup 10 Aug 4 23:39 .. drwxrwsr-x 59 nobody nogroup 59 Aug 27 19:36 drop drwxrwsr-x 6 nobody nogroup 11 Aug 27 19:36 sourceAside from some base permission issues it does have capabilities to read/write. Shoko is functioning as I would expect it to. Passing an LXC mount point in and assigning full permissions does seem to work.
Seems the root account specifically doesnt have root permissions though, dmesg resulted in unauthorized access, and despite enabling CIFS as an option in the initial configuration mount -a with a configuration in fstab still results as an access denied under a root account. Not a show stopper. I use Shoko mostly with Shokofin to create collections and organize metadata with Jellyfin so realistically it just needs read permissions on my anime folder so I can organize it. Otherwise working as expected.
Reacted by Daryush Balsara@colinrjrobbins @gwimbly03 I think what you both are experiencing is a classic LXC CIFS mount permission problem, the root user in LXC containers has the user ID 100000 so when the LXC root user wants to acces the CIFS Mount point from the host machine it tries accesing it with uid 100000, when you use the defaults in your CIFS mount it maps the permissions from your CIFS credentials to the root of the host with uid 0.
What you have to to is pass some arguments in the CIFS mount uid=100000 and forceuid should do the trick.
you can read more on that here: https://pve.proxmox.com/wiki/Unprivileged_LXC_containers
and also here https://pve.proxmox.com/wiki/Storage:_CIFSFeedback to the script: Commit 0ed5c55 (newest version on the helperscripts website) works fine for me, LXC Creation without any issues and for now it seems like shoko is doing its job well, i will update if any problems occur in the future
A PR has been created for shoko: community-scripts/ProxmoxVE#17617
Merged with #17617 in ProxmoxVE
Files deleted with PR #2341
Name of the Script
Shoko
Script Type
CT (LXC Container)
Does this script support arm64?
arm64 not supported
📋 Script Details
Shoko Server organizes anime collections — identifies files by hash against AniDB, pulls metadata from TvDB/TMDB/Trakt, exposes the result to Plex, Jellyfin and Kodi via plugins. Requested in discussion #7635.
No .NET SDK and no source build needed. The release assets look Windows-only at first glance (
Shoko.Setup.exe,Shoko.TrayService_win-x64.zip), butShoko.CLI_Framework_any-x64.zipis framework-dependent and cross-platform:publish/Shoko.CLIis a Linux ELF launcher next toShoko.CLI.dllShoko.CLI.runtimeconfig.jsonasks only forMicrosoft.NETCore.App 8.0.0+Microsoft.AspNetCore.App 8.0.0So
apt install aspnetcore-runtime-8.0— available in Debian trixie itself, no Microsoft repository required — plusprebuilddeployment of that zip. Upstream's documenteddotnet build -c=Release -r linux-x64path is not used; it would pull in the full SDK for no benefit.HOME=/opt/shoko_dataso the database and settings land outside the app directory and surviveCLEAN_INSTALLupdates.mediainfoandlibrhash0are installed for file analysis and hashing.has_arm: false— the asset is x64 only.Source: https://github.com/ShokoAnime/ShokoServer