[bug] Docker Compose version check in auto-install.sh fails on non-Debian systems (dpkg not found)

Open Beginner friendly
#771 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@shaneintentionboi06 is already working on this.

Since Nov 20, 2026.

  • #772 by @shaneintentionboi06 — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
docker-compose, shell
Domain
devops

Research direction

Start with deploy/auto-install.sh and the four failing upgrade tests in tests/runtests.py. Run the tests on a Linux system without dpkg to reproduce the failure, then inspect how the script checks the Docker Compose version. Done when the version check works without dpkg and all four tests pass.

Written by the indexing model from the issue text.

Description

bug

Describe the bug
tests/runtests.py upgrade tests fail on non-Debian systems because deploy/auto-install.sh uses dpkg --compare-versions to check the Docker Compose version. dpkg is Debian/Ubuntu-specific and isn't installed on distros like Arch or Fedora, so the check fails with dpkg: command not found, which the script misreports as "Docker Compose 2.33.1 or later is required."

Steps To Reproduce
Steps to reproduce the behavior:

  1. On a non-Debian system without dpkg installed, run make runtests.
  2. Observe the failing tests:
  • test_auto_install_upgrade_checks_compose_before_download
  • test_auto_install_upgrade_ignores_commented_settings
  • test_auto_install_upgrade_pulls_before_recreating_networks
  • test_auto_install_uses_selected_version

Expected behavior
The tests should pass on non-Debian systems too. The version check should use a tool available on all Linux distributions (e.g. sort -V) instead of dpkg, which is Debian/Ubuntu-specific.

System Information:

  • OS: Omarchy 4.5.0-3
  • Docker version: Docker version 29.9.2, build a82e528901
Dominant language
Python
Stars
207
Forks
128
Avg merge
13h 35m
Merged PRs (30d)
38

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openwisp/docker-openwisp

All issues in openwisp/docker-openwisp

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.