Open onlineapps-cloud opened 11 months ago
I encountered the same problem, and the only solution I found to update CasaOS is as follows:
sudo su
.cd
and hit enter.curl -fsSL https://get.casaos.io/update/v0.4.4-3 | sudo bash
to update to version 0.4.4-3.To make a fresh install of v0.4.4-3:
sudo su
.cd
and hit enter.curl -fsSL https://get.casaos.io/v0.4.4-3 | sudo bash
.I encountered the same problem, and the only solution I found to update CasaOS is as follows:
- Run
sudo su
.- Then type
cd
and hit enter.- And run
curl -fsSL https://get.casaos.io/update/v0.4.4-3 | sudo bash
to update to version 0.4.4-3.To make a fresh install of v0.4.4-3:
- Run
sudo su
.- Then type
cd
and hit enter.- And run
curl -fsSL https://get.casaos.io/v0.4.4-3 | sudo bash
.
Had the same issue. This worked great! thank you
hi, i saw that you release casaos v0.4.4.3 my version is: v0.4.4.2 Problem is that casaos don't give to update to v0.4.4.3. I tried to restart OS, but this not give positive results, how to detect update problem and fix it? best whishes.
1-2023-12-01_22.28.59.mp4
I also had this issue, but with the provided comment it solved part of the problem. I also have some issues where containers don't grab the latest version even tho creator/image:latest is set.
Would you say this is a issue for you as well? For example, i have a UptimeKuma instance running, current installed version is 1.23.3 but latest over at dockerhub is 1.23.8 and pressing "Check then update" tells me i got latest version and that there is no updates. casaos: UptimeKuma: Dockerhub:
about this problem i oppened issue, cannot update docker containers, also about maunal upgrade, this broke all my dockers container, i recovered system from backup, so it's not good idea to manual upgrade casaos.
Same issue with a fresh install at 0.4.4-3 and exporting a container from 0.4.4-2 to the new systems renders the container broken as it reports files e.g. gitea/conf/app.ini as not accessable even if they are there and opening fine in the cli.
uninstalling 0.4.4-3 and installing 0.4.4-2 fixed the issue for me
Same issue with a fresh install at 0.4.4-3 and exporting a container from 0.4.4-2 to the new systems renders the container broken as it reports files e.g. gitea/conf/app.ini as not accessable even if they are there and opening fine in the cli.
uninstalling 0.4.4-3 and installing 0.4.4-2 fixed the issue for me
This problem appeared for me in 0.4.4-2 so im not sure this is casaos version specific in this case. As im not great with docker, i don't really have knowledge to find what happens when i press the update button for specific containers. I would love to find out more in this in order to get som logs on the table.
Found a way around my update issue for containers, if i go to settings of the container and change the memory limit option, and press save it automagically downloads the new version when set to :latest figured this out by accident when i were checking things out for Uptime Kuma. Just a temporary fix if someone else got this issue.
Opening Settings and hitting Save without modifying also does the trick 😉
hi, i saw that you release casaos v0.4.4.3 my version is: v0.4.4.2 Problem is that casaos don't give to update to v0.4.4.3. I tried to restart OS, but this not give positive results, how to detect update problem and fix it? best whishes.
https://github.com/IceWhaleTech/CasaOS/assets/69077240/81617d8c-c657-47b1-b441-599533e096cc