Closed nuentes closed 11 months ago
The image does not need to be updated to get the latest commits, restart the container, or use the built-in updater.
I've restarted the container at least 6 times today already. I also restarted my entire server. I have also tried to update using the built in updater (settings -> system settings -> Updates -> install update). This appears as though it is working each time, however when the page refreshes, I am immediately greeted with a note that it is out of date.
Every other container I use, the image itself updates when there are new commits.
And the container logs say?
Linux a5d8697fe690 5.15.0-89-generic #99-Ubuntu SMP Mon Oct 30 20:42:41 UTC 2023 x86_64 GNU/Linux Time Zone: Etc/UTC [cont-init.d] 50-debug: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done.
Remove the lockfile it mentions,
Well, I had nothing to do with that file being there. But removing that file resolved the issue. Thank you
The image I keep pulling was created on 5/8/2022. I have branch set to v2-master. I can see this branch has updated very recently on https://github.com/causefx/Organizr. I keep getting alerts that Organizr has updates.