Unraid+Portainer.io: Docker container doesn't start. Gives exit code 135.

[Th0masDB]

DO NOT USE THIS FORM TO REPORT THAT A PARTICULAR WEBSITE IS NOT SCRAPING/WATCHING AS EXPECTED

This form is only for direct bugs and feature requests todo directly with the software.

Please report watched websites (full URL and any settings) that do not work with changedetection.io as expected IN THE DISCUSSION FORUMS or your report will be deleted

CONSIDER TAKING OUT A SUBSCRIPTION FOR A SMALL PRICE PER MONTH, YOU GET THE BENEFIT OF USING OUR PAID PROXIES AND FURTHERING THE DEVELOPMENT OF CHANGEDETECTION.IO

THANK YOU

Describe the bug
Docker container doesn't start. Gives exit code 135.

Version
Exact version in the top right area: 0.40.1.1

To Reproduce
Just update the container to 0.40.1.1

Expected behavior
The container to run ;-)

Screenshots

Desktop (please complete the following information):

• OS: Unraid 6.11.5

[Th0masDB]

Off topic, @dgtlmoon your sponsor button on the github page is broken. It just takes me to your profile. :)

[dgtlmoon]

@Th0masDB sorry but there is nothing me or anyone can do about this issue.. there's no debug logs or anything to help with, i'll move it to discussions

[dgtlmoon]

If you can attach some logs.. then someone can help, otherwise not much we can do

[Th0masDB]

The problem is that I do not get any logs because the container isn't starting....

[Th0masDB]

[dgtlmoon]

What does the "LOGS" button do that I can see?

[Th0masDB]

Also gives blanks... (the screenshot is from portainer.io btw)

[dgtlmoon]

I'm lost, so you run "portainer.io" inside "unraid" ? i havent used either

[Th0masDB]

okay, got you. lets begin with my setup, at home i have a server running Unraid OS. I use this for there raid support. Docker is pre installed and the I use portainer for managing my containers in Unraid. And sometimes use the terminal/CLI for debugging and trying the make things work :)

[dgtlmoon]

@Th0masDB aaah I know what it is, There was a fix for this #1336

I'll drop a new version

[Th0masDB]

Ahhh okay! Thanks! I will let you know if it solved it!

[dgtlmoon]

@Th0masDB could you try the :latest tag? https://hub.docker.com/layers/dgtlmoon/changedetection.io/latest/images/sha256-879ae5451b3022f2cfb658694c39ca42d1c3325ef7a65267c282ae437faa1fa9?context=explore and let me know if that container fixes it?

[Th0masDB]

Now, at the time of writing this, your push hasn't come through, and tried again with the :latest and unfortunately it still doesn't work.
When it does I will try again.

[dgtlmoon]

0.40.2 is building and should be out in roughly 1.5 hours when https://github.com/dgtlmoon/changedetection.io/actions/runs/4086817644 is done 🙏

[Th0masDB]

So today I tried the :latest and :dev. And unfortunately, it still gives the same error... :(
I really do not know what it is....

[Th0masDB]

Solution: reset the docker.img