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

[Bug]: Certain Arch distros aren't supported due to distro check logic #5297

Open
kamal-tufekcic opened this issue Mar 6, 2025 · 0 comments
Labels
🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization.

Comments

@kamal-tufekcic
Copy link

kamal-tufekcic commented Mar 6, 2025

Error Message and Logs

No error is provided (also a bug?)

Steps to Reproduce

  1. Run the setup script on either Garuda or Artix
  2. Script almost immediately exits

Example Repository URL

No response

Coolify Version

irrelevant

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Garuda/Artix/Others?

Additional Information

Many Arch-based distros use a different variant of "ID" in os-release, making this ineffective:
OS_TYPE=$(grep -w "ID" /etc/os-release | cut -d "=" -f 2 | tr -d '"')

In the case of Garuda for example, the value of "ID" will be "garuda", but instead there will be an "ID_LIKE" value that equals "arch", but this IMO adds unnecessary logic to the script, and is also not all encompassing, and a check such as that would still fail on Artix, which is completely distanced from Arch in every way, so I propose adding something like this in order to indiscriminately support all Arch-based distros:

    if command -v pacman; then
        OS_TYPE=arch
    fi
@kamal-tufekcic kamal-tufekcic added 🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization. labels Mar 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization.
Projects
None yet
Development

No branches or pull requests

1 participant