Problem Identified

1. BLE (Bluetooth Low Energy) initialization wasn't completing properly before containers needed access to the BLE device
   
2. Docker Compose service wasn't properly configured to start at system boot
   
3. Container startup timing was causing resource conflicts with the BLE device
   

Step-by-Step Solution

1. Create BLE initialization in the Docker Compose service

#Create the systemd service file

sudo cat > /etc/systemd/system/docker-compose-app.service << 'EOF'
[Unit]
Description=Docker Compose Application Service
After=docker.service network-online.target
Requires=docker.service network-online.target
Wants=network-online.target

[Service]
Type=oneshot
RemainAfterExit=yes
WorkingDirectory=/home/sudo5120/Eldar
ExecStartPre=/bin/bash -c "hciattach /dev/ttymxc3 any 115200 flow && sleep 2 && hciconfig hci0 up"
ExecStart=/usr/bin/docker compose up -d
ExecStop=/usr/bin/docker compose down

[Install]
WantedBy=multi-user.target
EOF

#Reload systemd configuration

sudo systemctl daemon-reload

#Enable the service to start at boot

sudo systemctl enable docker-compose-app.service

#Start the service manually to test

sudo systemctl start docker-compose-app.service

#Check service status

sudo systemctl status docker-compose-app.service

1. Unit section:
   
2. After=docker.service network-online.target: Ensures the service starts after Docker and network are available
   
3. Requires=docker.service network-online.target: Makes Docker and network mandatory dependencies
   
4. Wants=network-online.target: Ensures the service waits for the network to be fully online
   
5. Service section:
   
6. Type=oneshot: This service runs once and completes
   
7. RemainAfterExit=yes: Service is considered active even after the process exits
   
8. WorkingDirectory=/home/sudo5120/Eldar: Sets the working directory to where docker-compose.yml is located
   
9. ExecStartPre: Runs BLE initialization before starting containers
   
10. ExecStart: Starts Docker Compose in detached mode
    
11. ExecStop: Gracefully stops all containers when service is stopped
    
12. Install section:
    
13. WantedBy=multi-user.target: Service starts at normal boot time when system is ready for multi-user operation
    

4. Docker Compose configuration (already in place)

version: "3.3"
services:
  wait-for-network:
    image: alpine
    command: sh -c "until ping -c1 8.8.8.8; do sleep 5; done"
    restart: "no"
    network_mode: "host"  # Add this line to use host networking

  bvapi:
    image: *image"
    depends_on:
      - wait-for-network
    privileged: true
    devices:
    - "/dev/ttymxc3:/dev/hci0"
    restart: unless-stopped
    network_mode: "host"
    cap_add:
      - NET_ADMIN
    volumes:
      - type: volume
        source: bvapi-data
        target: /opt/sensorworks/api/data/
    logging:
      driver: json-file
      options:
        max-size: "10m"
        max-file: "5"
        compress: "true"

1. The wait-for-network container checks for internet connectivity before starting other containers
   
2. The bvapi container has access to the BLE device via /dev/ttymxc3 mapping
   
3. Persistent data is stored in the volume bvapi-data
   
4. Logs are properly managed with rotation to prevent disk space issues
   

5. Verifying successful setup

#Check if service started

sudo systemctl status docker-compose-app.service

#Check if containers are running

sudo docker ps

#Check BLE device status

hciconfig

1. System boots normally and starts Docker
   
2. The docker-compose-app service initializes BLE device
   
3. Docker Compose launches the wait-for-network container
   
4. Once network is confirmed available, the main bvapi container starts
   
5. BLE scanning service begins operation