Docker schedule-functions, maintenance and schedule-messages images restart loop after fresh install
- 0
- Self Hosted
this 3 docker images stuck in loop after fresh install. I had 1.5.4 and ran docker system prune -a to clean all docker images and volumes and tried to install 1.5.5
Pruning doesn't kill volumes, if you're trying a fresh install you need to remove the containers and volumes. If you're trying to update from 1.5.4 to 1.5.5 you need to do the upgrade cmd rather than the install.
https://appwrite.io/docs/advanced/self-hosting/update has the cmd
Thanks @Evdog before the prune command I ran the uninstall command from the docs docker compose down -v and before installing the new instance I cheked there was no volumes or images in all docker.
I am cleaning my server and removed everything intentionally.
I just pruned everything again just in case no images, volumes or networks are present. Also removed the Appwrite directory.
Is there any other place that I should remove Appwrite old files/cahce from?
Try bouncing the server just to be safe and install. If it still spins, post the logs from the looping containers and we can take a deeper look
do you mean restar the server?
yeah
does setting a custom mariadb user and pass from the .env could has anything to do with this?
Solved π
the issue was for some reason after removing docker volumes and images after restart some of them just pops back.
what I did:
docker compose down -v
remove all appwrite images and volumes
restart
remove everything again and then restart
and run docker compose up -d everything wokrs like charm
thanks @Evdog
Recommended threads
- CreateRow is doing ListRows on self-host...
### setup ``` appwrite 1.9.5 self-hosted bun 1.3 node-appwrite 27.1.0 ``` ### issue Im running a function on a self hosted 1.9.5 with "node-appwrite": "^27.1.0...
- Local function execution results in HTTP...
Hi all, I'm trying to develop a new function on my Ubuntu 24.04 machine running the latest version of docker. I've read through the documentation to install and...
- hi guys! my site is not accesible in my ...