Cannot upgrade mailcow, got errors when ./update.sh --check

[Widmo]

Hi,

I installed mailcow in May, now I tried to update it.

./update.sh --check
fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
Checking remote code for updates...
A problem occurred while trying to fetch the latest revision from github.

Just update.sh

./update.sh
fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
Checking internet connection... OK
Checking for newer update script...
fatal: 'origin' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
error: pathspec 'origin/HEAD' did not match any file(s) known to git
error: pathspec 'update.sh' did not match any file(s) known to git
Are you sure you want to update mailcow: dockerized? All containers will be stopped. [y/N]

Once confirmed, the containers stop.

Debian 10, no apparmor, VMware then docker, 4 core, 6 GB, docker 20.10.8, composer 1.29.2, no modification except official.

git diff origin/master
fatal: ambiguous argument 'origin/master': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

No dns problems.

[milkmaker]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[superstes]

Have seen this too. Hope this information helps someone:

I've had to revert an update before - maybe this broke it. (done as seen in the docs)

Checking remote code for updates...
A problem occurred while trying to fetch the latest revision from github.

This is how it looks:

# command used by the script
root@m02:/var/lib/mailcow# git rev-parse --abbrev-ref HEAD
HEAD

# current release
root@m02:/var/lib/mailcow# git describe --tags --abbrev=0
2024-05

# latest release
root@m02:/var/lib/mailcow# git describe --tags $(git rev-list --tags --max-count=1)
2024-07

This seems to be because the roll-back causes a detached HEAD in git:
https://circleci.com/blog/git-detached-head-state/
https://stackoverflow.com/questions/10228760/how-do-i-fix-a-git-detached-head

You can switch back to master via: git checkout master

Then it should look like this:

root@m02:/var/lib/mailcow# git rev-parse --abbrev-ref HEAD
master