Skip to content
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

Open
5 tasks done
0verEngineer opened this issue Jan 27, 2025 · 5 comments
Open
5 tasks done

update.sh broken #6267

0verEngineer opened this issue Jan 27, 2025 · 5 comments

Comments

@0verEngineer
Copy link

Contribution guidelines

I've found a bug and checked that ...

  • ... I understand that not following the below instructions will result in immediate closure and/or deletion of my issue.
  • ... I have understood that this bug report is dedicated for bugs, and not for support-related inquiries.
  • ... I have understood that answers are voluntary and community-driven, and not commercial support.
  • ... I have verified that my issue has not been already answered in the past. I also checked previous issues.

Description

I don't really know what the problem is or how to find it

The mailcow version shows 2025-01 now but this cannot be correct because the update did not work...

Logs:

./update.sh: line 31: syntax error near unexpected token `<'
./update.sh: line 31: `  done < <(git show "origin/${BRANCH}:docker-compose.yml" | grep "image:" | awk '{ gsub("image:","", $3); print $2 }')'

Steps to reproduce:

Try to run update.sh

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:

https://gist.github.com/0verEngineer/e4e073059b3298e9f819a9f26cb4a511

Logs of iptables -L -vn:

not needed

Logs of ip6tables -L -vn:

not needed

Logs of iptables -L -vn -t nat:

not needed

Logs of ip6tables -L -vn -t nat:

not needed

DNS check:

not needed
@DerLinkman
Copy link
Member

Can you tell me please WHICH Rocky Linux you use?

I cannot reproduce this on Rocky Linux 9

@0verEngineer
Copy link
Author

8.10

@DerLinkman
Copy link
Member

I see. But unfortunately can't reproduce there too...

@darthm1ke
Copy link

darthm1ke commented Jan 28, 2025

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

@0verEngineer
Copy link
Author

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?!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants