dependency failed to start: container runtipi-queue is unhealthy after upgrading to 4.5.2
Runtipi fails to start after the upgrade:
sudo ./runtipi-cli start
✓ User permissions are ok
✓ Copied system files
✓ Generated .env file
✓ File permissions ok
✓ Images pulled
✓ Existing containers stopped
✗ Failed to start containers
Debug: Container runtipi-db Creating
Container runtipi-queue Creating
Container runtipi-db Created
Container runtipi-queue Created
Container runtipi Creating
Container runtipi Created
Container runtipi-reverse-proxy Creating
Container runtipi-reverse-proxy Created
Container runtipi-queue Starting
Container runtipi-db Starting
Container runtipi-queue Started
Container runtipi-db Started
Container runtipi-db Waiting
Container runtipi-queue Waiting
Container runtipi-db Healthy
Container runtipi-queue Error
dependency failed to start: container runtipi-queue is unhealthy
sudo ./runtipi-cli start
✓ User permissions are ok
✓ Copied system files
✓ Generated .env file
✓ File permissions ok
✓ Images pulled
✓ Existing containers stopped
✗ Failed to start containers
Debug: Container runtipi-db Creating
Container runtipi-queue Creating
Container runtipi-db Created
Container runtipi-queue Created
Container runtipi Creating
Container runtipi Created
Container runtipi-reverse-proxy Creating
Container runtipi-reverse-proxy Created
Container runtipi-queue Starting
Container runtipi-db Starting
Container runtipi-queue Started
Container runtipi-db Started
Container runtipi-db Waiting
Container runtipi-queue Waiting
Container runtipi-db Healthy
Container runtipi-queue Error
dependency failed to start: container runtipi-queue is unhealthy
4 Replies
Can you share
docker logs runtipi-queueWARNING: 'guest_only_loopback' is deprecated, use '--default-user-only-loopback' instead
WARNING: 'guest_only_loopback' is deprecated, use '--default-user-only-loopback' instead
2025-10-25T13:18:03.315127Z INFO lmq[level: "Info", target: "stdout"] Logger settings
2025-10-25T13:18:03.315911Z INFO lmq.launcher LavinMQ 2.4.5
2025-10-25T13:18:03.315915Z INFO lmq.launcher Crystal 1.18.2 (2025-10-21)
2025-10-25T13:18:03.315915Z INFO lmq.launcher LLVM: 18.1.3
2025-10-25T13:18:03.315916Z INFO lmq.launcher Default target: x86_64-pc-linux-gnu
2025-10-25T13:18:03.315918Z INFO lmq.launcher Build flags: --release --debug
2025-10-25T13:18:03.315924Z INFO lmq.launcher Multithreading: 4 threads
2025-10-25T13:18:03.315930Z INFO lmq.launcher Pid: 1
2025-10-25T13:18:03.315931Z INFO lmq.launcher Config file: /etc/lavinmq/lavinmq.ini
2025-10-25T13:18:03.315933Z INFO lmq.launcher Data directory: /var/lib/lavinmq
2025-10-25T13:18:03.316124Z INFO lmq.launcher Max mmap count: 1048576
2025-10-25T13:18:03.316136Z INFO lmq.launcher FD limit: 1073741816
2025-10-25T13:18:03.331645Z INFO lmq.vhost[vhost: "/"] Loading default definitions
2025-10-25T13:18:03.331751Z INFO lmq.vhost[vhost: "/"] Compacting definitions
2025-10-25T13:18:03.334439Z INFO lmq.vhost_store Created vhost /
2025-10-25T13:18:03.344431Z INFO lmq.http.server Bound to 0.0.0.0:15672
2025-10-25T13:18:03.347113Z INFO lmq.http.server Bound to /tmp/lavinmqctl.sock
2025-10-25T13:18:03.348020Z INFO lmq.server Listening for AMQP on 0.0.0.0:5672
2025-10-25T13:18:03.348275Z INFO lmq.server Listening for MQTT on 0.0.0.0:1883
2025-10-25T13:18:03.348412Z INFO lmq.launcher Finished startup in 0.032042478s
WARNING: 'guest_only_loopback' is deprecated, use '--default-user-only-loopback' instead
WARNING: 'guest_only_loopback' is deprecated, use '--default-user-only-loopback' instead
2025-10-25T13:18:03.315127Z INFO lmq[level: "Info", target: "stdout"] Logger settings
2025-10-25T13:18:03.315911Z INFO lmq.launcher LavinMQ 2.4.5
2025-10-25T13:18:03.315915Z INFO lmq.launcher Crystal 1.18.2 (2025-10-21)
2025-10-25T13:18:03.315915Z INFO lmq.launcher LLVM: 18.1.3
2025-10-25T13:18:03.315916Z INFO lmq.launcher Default target: x86_64-pc-linux-gnu
2025-10-25T13:18:03.315918Z INFO lmq.launcher Build flags: --release --debug
2025-10-25T13:18:03.315924Z INFO lmq.launcher Multithreading: 4 threads
2025-10-25T13:18:03.315930Z INFO lmq.launcher Pid: 1
2025-10-25T13:18:03.315931Z INFO lmq.launcher Config file: /etc/lavinmq/lavinmq.ini
2025-10-25T13:18:03.315933Z INFO lmq.launcher Data directory: /var/lib/lavinmq
2025-10-25T13:18:03.316124Z INFO lmq.launcher Max mmap count: 1048576
2025-10-25T13:18:03.316136Z INFO lmq.launcher FD limit: 1073741816
2025-10-25T13:18:03.331645Z INFO lmq.vhost[vhost: "/"] Loading default definitions
2025-10-25T13:18:03.331751Z INFO lmq.vhost[vhost: "/"] Compacting definitions
2025-10-25T13:18:03.334439Z INFO lmq.vhost_store Created vhost /
2025-10-25T13:18:03.344431Z INFO lmq.http.server Bound to 0.0.0.0:15672
2025-10-25T13:18:03.347113Z INFO lmq.http.server Bound to /tmp/lavinmqctl.sock
2025-10-25T13:18:03.348020Z INFO lmq.server Listening for AMQP on 0.0.0.0:5672
2025-10-25T13:18:03.348275Z INFO lmq.server Listening for MQTT on 0.0.0.0:1883
2025-10-25T13:18:03.348412Z INFO lmq.launcher Finished startup in 0.032042478s
Okay weird it’s fine
I’m releasing 4.5.3 watch out in #📜・releases and try to update when it’s out
Removing the health check
Now it works as it should, thanks