I am posting this for suggestions and as a reference for those who may experience similar issues and will update this post on my progress to resolve the issue. I have just attempted to update RunTipi from version 3.8.4 to 3.9.1 (as root) and it seems to have broken RunTipi, though most Docker containers are still running (eg. AdGuard, Portainer…). I have installed RunTipi onto Armbian OS running on an Android TV-based SBC (M8S Pro with Amlogix S912). Prior to the update, RunTipi was running very well. After the update, I tried ./runtipi-cli debug via SSH which produced the following message:
Illegal instruction
Further, any command of `./runtipi-cli …" produces the same message and RunTipi, RunTipi-db, and Reverse-Proxy are all missing from Portainer. I updated RunTipi from the CLI as prompted from the web GUI using the following:
./runtipi-cli update v3.9.1
Which produced the following message:
✓ Tipi successfully stopped
✓ Releases fetched successfully
✓ Found version 3.9.1
✓ Tipi updated successfully. Starting new CLI
╔════════════════════════ Runtipi started successfully ════════════════════════╗
║ ║
║ Visit http://localhost:80 to access the dashboard ║
║ ║
║ You are now running version 3.9.1 ║
║ ║
║ Tipi is entirely written in TypeScript and we are looking for ║
║ contributors! ║
║ ║
╚══════════════════════════════════════════════════════════════════════════════╝
The error log (runtipi/logs/error.log) contains no new entries since the update. I will attempt to restore version 3.8.4 using the “Breaking Updates” page in the RunTipi documentation (Breaking updates – Runtipi).
Phew! Thank goodness for the great RunTipi Documentation! I successfully restored my broken update by reverting to 3.8.4 using the following as per the “Breaking updates” documentation:
✓ User permissions are ok
✓ Copied system files
✓ Generated .env file
✓ File permissions ok
✓ Images pulled
✓ Existing containers stopped
✓ Containers started
╔════════════════════════ Runtipi started successfully ════════════════════════╗
║ ║
║ Visit http://192.168.xxx.xxx:80 to access the dashboard ║
║ ║
║ Find documentation and guides at: https://runtipi.io ║
║ ║
║ Tipi is entirely written in TypeScript and we are looking for ║
║ contributors! ║
║ ║
╚══════════════════════════════════════════════════════════════════════════════╝
I will attempt to update again after a complete backup and will post a follow-up on my progress. The next update will follow the “Breaking updates” documentation instead of the ./runtipi-cli update v3.9.1 under “How to Update” in the Settings tab of the web UI.
Hello, you seem to be in a very unique setup We only test and officially support Debian based OS so it might be complicated for us to pinpoint what’s the issue here. Since you get those errors using the CLI, it is probably one of our Rust dependencies we have updated that is not supported. We’ll try to get the most up to date versions of our CLI dependencies
Thanks for the support! I’m running a fork of Armbian which is Debian-based so it should work okay with RunTipi even though I have a unique setup. I still haven’t found the exact problem with the update script (./runtipi-cli update v3.9.1), but the result affected my boot partition causing a major fault with the OS. I was able to recover from that and ended up rebuilding using backups for my various containers, and have now updated RunTipi successfully to v.3.9.3 using the following method:
Stop RunTipi (everything done as root)
./runtipi-cli stop
Stop all docker containers (sometimes they keep running after RunTipi is stopped)
docker stop $(docker ps -a -q)
Check for active containers in docker (should be none)
I recommend updating RunTipi using the above for anyone using Armbian on an Android TV box, especially those that utilize a separate FAT partition for boot (eg. AmLogic s9xx, or s912 in my case). I’m kinda’ amateur, but I’ll try my best to support anyone wanting to host RunTipi on anything similar as it’s a great learning experience and you can self-host with incredibly low power consumption. I’m running 19 containers / “Apps”, including WordPress, Joplin, AdGuard and using around 2 watts of power. Thanks so much to the devs for a great system - I’m having tons of fun!!!
We only test and officially support Debian based OS so it might be complicated for us to pinpoint what’s the issue here. Since you get those errors using the CLI, it is probably one of our Rust dependencies we have updated that is not supported. We’ll try to get the most up to date versions of our CLI dependencies