optiman Posted August 22, 2022 Share Posted August 22, 2022 Ok, thanks for looking into it. I'll just stay where I'm at until you confirm it's ok to move the latest. I'm happy to test it when you're ready. Quote Link to comment
optiman Posted September 27, 2022 Share Posted September 27, 2022 @binhex I hope you are doing well. How will we know when the UI issue is fixed? I have my docker set to specifically get v2022.02.20-01 and I'm waiting to change the config to "latest". On another note regarding all of your popular docker apps, I was just reading that upgrading to 6.11 requires the removal of Nerdpack. Some plugins are now part of unraid, but others have to be manually installed if they are still required. One of the dockers I installed (maybe more) included instructions to install NP to add perl, unrar, Python, etc. I don't recall if it was any of yours. Does any of your dockers need any of these apps? If not, I'm going to uninstall the above and NP and upgrade to 6.11. If they are still needed, I'll have to dl and install manually now before upgrading to 6.11. Thanks! Quote Link to comment
binhex Posted September 28, 2022 Author Share Posted September 28, 2022 11 hours ago, optiman said: I hope you are doing well. How will we know when the UI issue is fixed? you will have to try pulling down latest to confirm if the issue is resolved. 11 hours ago, optiman said: One of the dockers I installed (maybe more) included instructions to install NP to add perl, unrar, Python, etc. I don't recall if it was any of yours. Does any of your dockers need any of these apps? nope. Quote Link to comment
optiman Posted October 3, 2022 Share Posted October 3, 2022 For those using v2022.02.20-01, you can now upgrade to the latest version. The gui issue was fixed. 1 Quote Link to comment
wildwolf Posted October 5, 2022 Share Posted October 5, 2022 Currently running sickchill on a synology, but that presents a msg that it's no longer supported. I have an unRAID server, and found this thread. Is this a similar sickchill? Same sickchill? Running in a docker on unRAID seems desirable to me. I think I could then get rid of my synology. Is there a good howto/video for installing sickchill on unRAID docker from scratch? I'm assuming I can't easily port any thing over and would just need to start from scratch. Quote Link to comment
nick5429 Posted July 25 Share Posted July 25 Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2024-07-25 14:24:41.201040 [info] Host is running unRAID 2024-07-25 14:24:41.257635 [info] System information Linux 12937845fbd7 6.1.79-Unraid #1 SMP PREEMPT_DYNAMIC Fri Mar 29 13:34:03 PDT 2024 x86_64 GNU/Linux 2024-07-25 14:24:41.311686 [info] PUID defined as '99' 2024-07-25 14:24:41.401049 [info] PGID defined as '100' 2024-07-25 14:24:41.495063 [info] UMASK defined as '000' 2024-07-25 14:24:41.545407 [info] Permissions already set for '/config' 2024-07-25 14:24:41.630897 [info] Deleting files in /tmp (non recursive)... 2024-07-25 14:24:42.005329 [info] Starting Supervisor... 2024-07-25 14:24:42,748 INFO Included extra file "/etc/supervisor/conf.d/sickchill.conf" during parsing 2024-07-25 14:24:42,748 INFO Set uid to user 0 succeeded 2024-07-25 14:24:42,757 INFO supervisord started with pid 7 2024-07-25 14:24:43,759 INFO spawned: 'start-script' with pid 47 2024-07-25 14:24:43,760 INFO reaped unknown pid 8 (exit status 0) 2024-07-25 14:24:44,762 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2024-07-25 14:24:45,028 DEBG 'start-script' stderr output: /home/nobody/start.sh: line 7: 49 Illegal instruction "${install_path}/bin/sickchill" --config /config/config.ini --datadir /config 2024-07-25 14:24:45,028 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22418072691408 for <Subprocess at 22418073011728 with name start-script in state RUNNING> (stdout)> 2024-07-25 14:24:45,028 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22418085474448 for <Subprocess at 22418073011728 with name start-script in state RUNNING> (stderr)> 2024-07-25 14:24:45,028 WARN exited: start-script (exit status 132; not expected) 2024-07-25 14:24:45,029 DEBG received SIGCHLD indicating a child quit Docker fails to start I rolled back to binhex/arch-sickchill:2024.2.18-01 a while back; tried again today and it's still failing Quote Link to comment
binhex Posted July 25 Author Share Posted July 25 5 hours ago, nick5429 said: Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2024-07-25 14:24:41.201040 [info] Host is running unRAID 2024-07-25 14:24:41.257635 [info] System information Linux 12937845fbd7 6.1.79-Unraid #1 SMP PREEMPT_DYNAMIC Fri Mar 29 13:34:03 PDT 2024 x86_64 GNU/Linux 2024-07-25 14:24:41.311686 [info] PUID defined as '99' 2024-07-25 14:24:41.401049 [info] PGID defined as '100' 2024-07-25 14:24:41.495063 [info] UMASK defined as '000' 2024-07-25 14:24:41.545407 [info] Permissions already set for '/config' 2024-07-25 14:24:41.630897 [info] Deleting files in /tmp (non recursive)... 2024-07-25 14:24:42.005329 [info] Starting Supervisor... 2024-07-25 14:24:42,748 INFO Included extra file "/etc/supervisor/conf.d/sickchill.conf" during parsing 2024-07-25 14:24:42,748 INFO Set uid to user 0 succeeded 2024-07-25 14:24:42,757 INFO supervisord started with pid 7 2024-07-25 14:24:43,759 INFO spawned: 'start-script' with pid 47 2024-07-25 14:24:43,760 INFO reaped unknown pid 8 (exit status 0) 2024-07-25 14:24:44,762 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2024-07-25 14:24:45,028 DEBG 'start-script' stderr output: /home/nobody/start.sh: line 7: 49 Illegal instruction "${install_path}/bin/sickchill" --config /config/config.ini --datadir /config 2024-07-25 14:24:45,028 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22418072691408 for <Subprocess at 22418073011728 with name start-script in state RUNNING> (stdout)> 2024-07-25 14:24:45,028 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22418085474448 for <Subprocess at 22418073011728 with name start-script in state RUNNING> (stderr)> 2024-07-25 14:24:45,028 WARN exited: start-script (exit status 132; not expected) 2024-07-25 14:24:45,029 DEBG received SIGCHLD indicating a child quit Docker fails to start I rolled back to binhex/arch-sickchill:2024.2.18-01 a while back; tried again today and it's still failing just tested and it works for me, i can see the web ui, so i can only conclude that your config is causing the issue, try renaming your host path for /config so that the container re-creates it then reconfigure the app. Quote Link to comment
nick5429 Posted August 1 Share Posted August 1 On 7/25/2024 at 7:44 PM, binhex said: just tested and it works for me, i can see the web ui, so i can only conclude that your config is causing the issue, try renaming your host path for /config so that the container re-creates it then reconfigure the app. A brand new copy of this container with none of the default populated settings changed, into a blank config directory, fails in exactly the same way on my system Copying my full config directory and pointing the latest top of tree version of the LSIO sickchill container at it seems to work Quote Link to comment
binhex Posted August 1 Author Share Posted August 1 9 minutes ago, nick5429 said: A brand new copy of this container with none of the default populated settings changed, into a blank config directory, fails in exactly the same way on my system Copying my full config directory and pointing the latest top of tree version of the LSIO sickchill container at it seems to work Sorry just tried it again, clean config, no previous image and it came straight up!, what version of unraid are you using? for ref im using 6.12.10 Quote Link to comment
nick5429 Posted August 1 Share Posted August 1 1 minute ago, binhex said: Sorry just tried it again, clean config, no previous image and it came straight up!, what version of unraid are you using? for ref im using 6.12.10 I'm on 6.12.11 Docker start command shows as: docker run -d --name='binhex-sickchill-fresh' --net='bridge' -e TZ="America/New_York" -e HOST_OS="Unraid" -e HOST_HOSTNAME="nickserver" -e HOST_CONTAINERNAME="binhex-sickchill-fresh" -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8081]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/sickchill-icon.png' -p '8091:8081/tcp' -v '/mnt/user/appdata/data':'/data':'rw' -v '/mnt/user':'/media':'rw' -v '/mnt/disks/SanDiskSSD/appdata/binhex-sickchill-fresh':'/config':'rw' 'binhex/arch-sickchill' Manually running /home/nobody/start.sh didn't give me any additional info beyond the prior 'illegal instruction' Redirecting the config/install dir back onto /mnt/user/appdata didn't change anything Quote Link to comment
nick5429 Posted August 1 Share Posted August 1 fwiw this post isn't me; appears somebody else had this same problem: Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.