Skip to content

Karakeep update writes wrong version into karakeep.envΒ #14369

@Hexus0101

Description

@Hexus0101

βœ… Have you read and understood the above guidelines?

yes

πŸ”Ž Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

πŸ“œ What is the name of the script you are using?

Karakeep

πŸ“‚ What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/karakeep.sh)"

βš™οΈ What settings are you using?

  • Default Settings
  • Advanced Settings

πŸ–₯️ Which Linux distribution are you using?

Debian 13

πŸ“ˆ Which Proxmox version are you on?

9.1.6

πŸ“ Provide a clear and concise description of the issue.

Bug: KaraKeep update writes wrong SERVER_VERSION to karakeep.env

Description

When updating KaraKeep via the Proxmox community script, the script writes the wrong version into:

/etc/karakeep/karakeep.env

The issue appears to be caused by the variable CHECK_UPDATE_RELEASE being reused globally.

The script first checks the Karakeep GitHub release:

if check_for_gh_release "karakeep" "karakeep-app/karakeep"; then

Then it deploys KaraKeep:

CLEAN_INSTALL=1 fetch_and_deploy_gh_release "karakeep" "karakeep-app/karakeep" "tarball"

Later, the script calls:

setup_meilisearch

After that, it writes the version to karakeep.env using:

sed -i "s/^SERVER_VERSION=.*$/SERVER_VERSION=${CHECK_UPDATE_RELEASE#v}/" /etc/karakeep/karakeep.env

The problem is that CHECK_UPDATE_RELEASE no longer necessarily contains the Karakeep release at this point. It seems to have been overwritten by the Meilisearch (current version 1.43.0) update/check logic.

πŸ”„ Steps to reproduce the issue.

Update Karakeep and check the Version in the karakeep.env

❌ Paste the full error output (if available).

πŸ–ΌοΈ Additional context (optional).

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions