restart after freshinstall fails - dependency failed to start: container runtipi is unhealthy
Hi,
I have installed runtipi on a raspberry pi with raspberry OS using
curl -L https://setup.runtipi.io | bash. In order to expose apps to web I am using the cloudflared tunnel as explained on the documentation and it worked well.
There is nothing of significance as yet and I am still trying to familiarise myself with runtipi-cli. Next, I wanted to stop, start and restart runtipi and that is where I am encountering the problem.
I am able to recreate this problem every single time. I create a fresh install and it runs fine the first time and then when I try restarting it I get this same error.
Please can someone help me identify what I might be doing wrong? I have included all logs in text file.
11 Replies
Hi ! What model of raspberry do you have ?
it is 3b with 4G in swap. I can see that when I downgrade to 3.9.4 the stop and start works fine so looks like its the latest runtipi-cli that causes this problem.
You have less than 1 GB memory, this is not sufficient to be able to use runtipi
but it runs the first time. and with previous version it starts the second time as well so I don't think it is hardware related but if you think it is which logs can help me establish this for a fact?
Runtipi needs at least 500MB of RAM, then we have the rabbitmq queue, the database and traefik. If you add to this the apps you install on it, it will never hold together.
You can use the command
free -h to see your RAM usage. try to run it while it's "starting"
Or install htop for a more detailed usagelike I said in begining there are no apps installed just plain vanilla runtipi... and it does work with fresh install on both 4.4.4 as well as 3.9.4. With 4.4.4 restart and start fail but with 3.9.4 they do not. It is a completely blank raspberrypi - nothing on it at all. I will share free -h in a sec
Docker alone requires 4GB of RAM https://docs.docker.com/desktop/setup/install/linux/#general-system-requirements
Docker Documentation
Linux
Install Docker on Linux with ease using our step-by-step installation guide covering system requirements, supported platforms, and where to go next.
While it may work, if you see crashes without logs it is most probably an out of memory issue
I would not be using this setup for when I have got my head around the whole thing. I was only trying runtipi more as a way of evaluating if it will fit my needs and at the moment this problem appears to be a blocker. I will trust you if you say it is memory issue but how does that explain restart and start working with previous version but failing with latest one. Even if I upgrade to latest version it does work so it does feel like there is something different in the runtipi-cli version which causes this obscure issue. Anyway, I can't try it on any other hardware so perhaps i will have to leave it here.
The cli isn’t doing much than copying files and starting a few docker containers. Sorry, I didn’t understand clearly that you were able to run 4.4.4 but only the start and stop were failing
The update tho does a full start with the new cli when it successfully downloads the new version so it is a bit strange that a normal start wouldn’t work
Could you try to check
sudo journalctl -fu docker.service when it fails to see what the docker daemon is unhappy about?Try to see if you can extract some logs https://docs.docker.com/engine/daemon/logs/