Here we have the issue where the docker container fails without proper error logging, again... :(

@nucleogenic can you please remind me how to troubleshoot this?

Hey @rdmark!

Check the logs in the Github Action if you haven't already:

They're under the 'Summary' tab:

I'm seeing the following in web.log:

docker-web-1  | INFO: pip is looking at multiple versions of bjoern to determine which version is compatible with other requirements. This could take a while.
docker-web-1  | ERROR: Cannot install -r requirements.txt (line 2) and werkzeug==2.2.3 because these package versions have conflicting dependencies.
docker-web-1  | 
docker-web-1  | The conflict is caused by:
docker-web-1  |     The user requested werkzeug==2.2.3
docker-web-1  |     flask 2.3.2 depends on Werkzeug>=2.3.3
docker-web-1  | 
docker-web-1  | To fix this you could try to:
docker-web-1  | 1. loosen the range of package versions you've specified
docker-web-1  | 2. remove package versions to allow pip attempt to solve the dependency conflict
docker-web-1  | 
docker-web-1  | ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/user_guide/#fixing-conflicting-dependencies

If that doesn't mean anything to you, or you think it's a Docker env specfic issue, give me a shout and I'll take a more in-depth look!

Found where the log is, thank you! I'll try to remember this for the next time. ;)

The tests pass now so this is ready for your review.

Please note that I'm living out of a hotel right now without access to my piscsi gear. So I have only tested as far as the web app launching (and then dying because the piscsi backend can't start up.)

Hi folks, I'm glad this was resolved and closed, but this fix needs to be rolled into main and previous releases. None of the previous tags nor precompiled images work at this point. Every install will fail since the wrong version of werkzeug gets installed by default.