WSL1 legacy build not working

[pandafeliz]

LRR Version and OS
LANraragi 0.9.3 legacy WLS1 build, Windows 11

Bug Details
Clean installation, it crashes at start, still running legacy build because otherwise I can't use redis for Windows.

Matching Logs

Making sure the WSL distro is using specified WSL mode: 1.
The operation completed successfully.
Executing the following command on WSL: export LRR_NETWORK=http://*:3000 && export LRR_DATA_DIRECTORY='/mnt/c/lrr/manga' && export LRR_THUMB_DIRECTORY='/mnt/c/cache/lrr' && cd /home/koyomi/lanraragi && rm -f public/temp/server.pid && mkdir -p log && mkdir -p content && mkdir -p database && sysctl vm.overcommit_memory=1 && redis-server /home/koyomi/lanraragi/tools/build/docker/redis.conf --dir '/mnt/c/lrr/manga/' --daemonize yes && perl ./script/launcher.pl -f ./script/lanraragi
vm.overcommit_memory = 1
Server PID will be at /home/koyomi/lanraragi/public/temp/server.pid
Attempting to create directory /root/perl5
Can't load application from file "/home/koyomi/lanraragi/script/lanraragi": Perl v5.36.0 required--this is only v5.30.3, stopped at /home/koyomi/lanraragi/script/../lib/LANraragi/Model/Plugins.pm line 3.
BEGIN failed--compilation aborted at /home/koyomi/lanraragi/script/../lib/LANraragi/Model/Plugins.pm line 3.
Compilation failed in require at /home/koyomi/lanraragi/script/../lib/LANraragi/Model/Upload.pm line 21.
BEGIN failed--compilation aborted at /home/koyomi/lanraragi/script/../lib/LANraragi/Model/Upload.pm line 21.
Compilation failed in require at /home/koyomi/lanraragi/script/../lib/LANraragi/Utils/Minion.pm line 18.
BEGIN failed--compilation aborted at /home/koyomi/lanraragi/script/../lib/LANraragi/Utils/Minion.pm line 18.
Compilation failed in require at /home/koyomi/lanraragi/script/../lib/LANraragi.pm line 19.
BEGIN failed--compilation aborted at /home/koyomi/lanraragi/script/../lib/LANraragi.pm line 19.
Compilation failed in require at (eval 90) line 1.

[Difegue]

Oh hmm that's bad, we started using try/catch in a few spots in 0.9.3 and that requires at least Perl 5.34.0 - We moved to require 5.36 in those because it cleaned up signatures as well.

I'm not sure if there are backports of that to the old Alpine version legacy builds use.

[Difegue]

I've updated the legacy Dockerfile/Windows builds to backport Perl 5.38 -- It should function but I lost imagemagick in the process, so you won't have working thumbnails.
38 should at least give you some margin, I don't see us requiring past 36 for a little while.

We're kinda kicking the can down here - It's likely possible to rebuild the ImageMagick module properly on Alpine 3.12 but that's more effort than I'm willing to dedicate to WSL1 and old Synology hardware at this point.

[pandafeliz]

Thanks for the effort, I know is more hassle than is worth it to maintain the WSL1 build but I can't get my db work with the bundled redis on any version and this setup has been working fine

EDIT:
Tried the latest nightly and now getting this error

Making sure the WSL distro is using specified WSL mode: 1.
The operation completed successfully.
Executing the following command on WSL: export LRR_NETWORK=http://*:3000 && export LRR_DATA_DIRECTORY='/mnt/c/lrr/manga' && export LRR_THUMB_DIRECTORY='/mnt/c/cache/lrr' && cd /home/koyomi/lanraragi && rm -f public/temp/server.pid && mkdir -p log && mkdir -p content && mkdir -p database && sysctl vm.overcommit_memory=1 && redis-server /home/koyomi/lanraragi/tools/build/docker/redis.conf --dir '/mnt/c/lrr/manga/' --daemonize yes && perl ./script/launcher.pl -f ./script/lanraragi
vm.overcommit_memory = 1
No such signal: SIGPIPE at /opt/perl/lib/site_perl/5.38.0/Mojo/IOLoop.pm line 26.
Server PID will be at /home/koyomi/lanraragi/public/temp/server.pid
Attempting to create directory /root/perl5
Can't load application from file "/home/koyomi/lanraragi/script/lanraragi": Can't locate Image/Magick.pm in @INC (you may need to install the Image::Magick module) (@INC entries checked: /root/perl5/lib/perl5/5.38.0/x86_64-linux-thread-multi /root/perl5/lib/perl5/5.38.0 /root/perl5/lib/perl5/x86_64-linux-thread-multi /root/perl5/lib/perl5 /home/koyomi/lanraragi/script/../lib /opt/perl/lib/site_perl/5.38.0/x86_64-linux-thread-multi /opt/perl/lib/site_perl/5.38.0 /opt/perl/lib/5.38.0/x86_64-linux-thread-multi /opt/perl/lib/5.38.0) at /home/koyomi/lanraragi/script/../lib/LANraragi/Utils/Archive.pm line 21.
BEGIN failed--compilation aborted at /home/koyomi/lanraragi/script/../lib/LANraragi/Utils/Archive.pm line 21.
Compilation failed in require at /home/koyomi/lanraragi/script/../lib/LANraragi/Utils/Database.pm line 23.
BEGIN failed--compilation aborted at /home/koyomi/lanraragi/script/../lib/LANraragi/Utils/Database.pm line 23.
Compilation failed in require at /home/koyomi/lanraragi/script/../lib/LANraragi/Utils/Plugins.pm line 8.
BEGIN failed--compilation aborted at /home/koyomi/lanraragi/script/../lib/LANraragi/Utils/Plugins.pm line 8.
Compilation failed in require at /home/koyomi/lanraragi/script/../lib/LANraragi.pm line 16.
BEGIN failed--compilation aborted at /home/koyomi/lanraragi/script/../lib/LANraragi.pm line 16.
Compilation failed in require at (eval 132) line 1.

I reverted back to the last working version I have in the meantime

[Difegue]

Right, I think at some point the server stopped failing gracefully when the Magick bindings weren't available. (That mightve been when we switched to said bindings instead of doing CLI magick invocations actually..)

I've pushed another fix for that since it's not really costing much at this point. (And I get to do more 5.36 conversion which is nice)