arm/v7 1.5.20 not starting due to missing libssl

cleggton commented 1 month ago

Tandoor Version

??

Setup

Docker / Docker-Compose

Reverse Proxy

No reverse proxy

Other

No response

Bug description

Since the update to the Docker containers since the 9th October the web component of the stack isn't starting due to missing libssl.

Part of me wonders if this is an issue with the host or the Alpine base image, unsure where to start.

Compose listed below:

`version: "3" services: db_recipes: restart: always image: postgres:15-alpine volumes:

./postgresql:/var/lib/postgresql/data env_file:
stack.env

web_recipes: restart: always image: vabene1111/recipes env_file:
stack.env volumes:
staticfiles:/opt/recipes/staticfiles
Do not make this a bind mount, see https://docs.tandoor.dev/install/docker/#volumes-vs-bind-mounts
nginx_config:/opt/recipes/nginx/conf.d
./mediafiles:/opt/recipes/mediafiles depends_on:
db_recipes

nginx_recipes: image: nginx:mainline-alpine restart: always ports:
80:80 env_file:
stack.env depends_on:
web_recipes volumes:
Do not make this a bind mount, see https://docs.tandoor.dev/install/docker/#volumes-vs-bind-mounts
nginx_config:/etc/nginx/conf.d:ro
staticfiles:/static:ro
./mediafiles:/media:ro

volumes: nginx_config: staticfiles:`

Relevant logs

ImportError: Error loading shared library libssl.so.1.1: No such file or directory (needed by /opt/recipes/venv/lib/python3.12/site-packages/cryptography/hazmat/bindings/_rust.abi3.so)

[2024-10-11 15:35:15 +0200] [15] [INFO] Worker exiting (pid: 15)

[2024-10-11 13:35:15 +0000] [1] [ERROR] Worker (pid:13) exited with code 3

[2024-10-11 13:35:15 +0000] [1] [ERROR] Worker (pid:14) was sent SIGTERM!

[2024-10-11 13:35:15 +0000] [1] [ERROR] Worker (pid:15) was sent SIGTERM!

[2024-10-11 13:35:15 +0000] [1] [ERROR] Shutting down: Master

[2024-10-11 13:35:15 +0000] [1] [ERROR] Reason: Worker failed to boot.

smilerz commented 1 month ago

What image are you running? Can you delete the container and image and then redeploy it?

cleggton commented 1 month ago

using vabene1111/recipes:latest

I will recreate the container and see what happens

cleggton commented 1 month ago

still the same error. I can copy the complete log here if helpful

smilerz commented 1 month ago

I don't have arm so can't test - I'd recommend going back to 1.5.19

vabene1111 commented 1 month ago

is this arm/v7 architecture on some older PI or something?

Just FYI: I just dropped support for that on the tandoor 2 branch because it just always causes issues.

cleggton commented 1 month ago

@vabene1111 it is arm/v7 on a pi3 i think.

vabene1111 commented 1 month ago

ok. Sorry but I am afraid I lack the time to support this platform. It seems to break every few month and its always a pain to get it back working. Feel free to play around and if you fix it I will implement the fix for the 1.x line of tandoor but 2.x will drop support for it, at least offically (you can always manually install/make your own container).

I am sorry about this but I hardly have enough time to support the basic app, so no time to support this.

cleggton commented 1 month ago

For completeness, reverting to 1.5.19 and restarting all the containers gets this running again. I will try and work out what is going on with 1.5.20 and post back here if i have an update

vabene1111 commented 1 month ago

sometimes packages are missing/broken for arm/v7 only for some time (mostly after updates) so maybe a new release will fix this automatically. sadly I do not think I can delete just a single architecture from a tag on docker hub so there might be others running into this issue.

TandoorRecipes / recipes