-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update.sh broken #6267
Comments
Can you tell me please WHICH Rocky Linux you use? I cannot reproduce this on Rocky Linux 9 |
8.10 |
I see. But unfortunately can't reproduce there too... |
I am having the same issue, I have stopped my containers, run the update.sh it updated, and then I brought eveyrhing back up and it still tells me that 2025 update is available, I am not surewhy this is happening, I am on ubuntu 22.04 with updates as well 64bit. It still show as if I am on: 2023-10aThere is an update available 2025-01 -- [2023-10a](https://mail.theworkloophn.com/debug#)There is an update available 2025-01 BTW, the only reason I was updating is because I was trying to access some inofrmation via the API, and the API directory was empty, I thought it might have been erased or not pulled, so I decied to update and still API not working and the update is prompting me to update again |
This does not seem like the same issue at all?! |
Contribution guidelines
I've found a bug and checked that ...
Description
Logs:
Steps to reproduce:
Which branch are you using?
master
Which architecture are you using?
x86
Operating System:
Rocky Linux
Server/VM specifications:
Enough
Is Apparmor, SELinux or similar active?
yes
Virtualization technology:
KVM
Docker version:
26.1.3
docker-compose version or docker compose version:
v2.27.0
mailcow version:
2025-01
Reverse proxy:
Nginx
Logs of git diff:
Logs of iptables -L -vn:
Logs of ip6tables -L -vn:
Logs of iptables -L -vn -t nat:
Logs of ip6tables -L -vn -t nat:
DNS check:
The text was updated successfully, but these errors were encountered: