From 71b68aba36f871aacc268826d332ecebee58c641 Mon Sep 17 00:00:00 2001 From: torlando-tech Date: Sat, 15 Nov 2025 20:17:37 -0500 Subject: [PATCH] fix(ci): Skip BlueZ LE-only mode configuration in containers MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Fixes installer failures in container environments due to missing sudo command. The BlueZ LE-only mode configuration section was attempting to modify /etc/bluetooth/main.conf using sudo, even in container environments where: 1. Bluetooth hardware is not available 2. sudo is often not installed (containers run as root) 3. BlueZ configuration is not applicable Now detects container environments using is_container() and skips the LE-only mode configuration entirely, consistent with the Bluetooth adapter power state checks. This prevents "sudo: command not found" errors in Debian/Ubuntu CI containers. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- install.sh | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/install.sh b/install.sh index f923d11..f0563ae 100755 --- a/install.sh +++ b/install.sh @@ -761,7 +761,13 @@ echo # Step 5C: BlueZ LE-Only Mode Configuration print_header "BlueZ LE-Only Mode Configuration" -if ! command -v bluetoothctl &> /dev/null; then +# Skip BlueZ configuration in container environments (no hardware access) +if is_container; then + print_info "Container environment detected - skipping BlueZ LE-only mode configuration" + print_warning "BlueZ configuration is not applicable in containers" + print_info "This is expected behavior for CI/testing environments" + echo +elif ! command -v bluetoothctl &> /dev/null; then print_warning "bluetoothctl not found - skipping LE-only mode configuration" echo elif [ ! -f /etc/bluetooth/main.conf ]; then