dependency failed to start: container wger_server is unhealthy
Victorivus opened this issue · comments
I am unable to launch it, all containers get launched except for wger_server.
After executing the apt-get install -y libjpeg-turbo8
it just exits.
dependency failed to start: container wger_server is unhealthy
services:
web:
user: root
image: wger/server:latest
container_name: wger_server
depends_on:
db:
condition: service_healthy
cache:
condition: service_healthy
env_file:
- ./config/prod.env
volumes:
- static:/home/wger/static
- media:/home/wger/media
expose:
- 8000
command: apt-get install -y libjpeg-turbo8
healthcheck:
test: wget --no-verbose --tries=1 --spider http://localhost:8000
interval: 1000s
timeout: 5000s
retries: 5
restart: unless-stopped
When relaunching without down, I get:
Can someone help me? Let me know if you need more information.
Hardware: Raspberry Pi 2 Model B Rev 1.1
(ARMv7 Processor rev 5 (v7l)
)
OS version: #1 SMP Raspbian 1:6.6.20-1+rpt1 (2024-03-07)
Do you know if the raspi is arm/v7 or arm64? I know that with a pi 4 everything works fine but there might be some problems with an older one (getting the images to build was a bit of a pain)
Raspberry Pi 2 Model B Rev 1.1
ARMv7 Processor rev 5 (v7l)
So can I forget about running this? 🥲
Well, without any kind of error message of any kind it will be difficult 😅 I'm also wondering why this breaks right at the beginning, even if there were some problems with the package, I'd expect the server to at least start
BTW, why did you install the jpeg package?
I could step a bit forward. I built the image independantly with the following Dockerfile
:
FROM wger/server
USER root
RUN apt install -y libjpeg-turbo8
Build with: docker build -t wger/server:rasp .
Edited the docker-compose.yml
to image: wger/server:rasp
and erase command:...
and then docker compose up
.
Then got inside the container (docker exec -it 9e******f650 sh
and executed:
apt install libxcb1 -y
docker compose restart web
for the moment it is running the migrations (don't know what to expect, it is stil running...)
You can set Django_debug to false in the env file, then you should get a detailed traceback in the browser
I think the OS was too old, after spending too any hours I couldn't make it work. I finally have installed it in a newer system and works fine.