jlpoole/ble-reticulum
1
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

fix(ci): Skip BlueZ LE-only mode configuration in containers

Browse source 
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 <noreply@anthropic.com>
This commit is contained in:
torlando-tech 2025-11-15 20:17:37 -05:00
commit b336b73396
1 changed files with 7 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

8
install.sh
View file

@ -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