For installation on Raspberry Pi 5, download and run the setup script with a single command:
curl -sSL https://raw.githubusercontent.com/Neurotech-Hub/Hublink-Hypervisor-Setup/main/setup.sh | sudo bashThis script will:
- Create the installation directory at
/opt/hublink-hypervisor - Clone the latest configuration files
- Pull the latest Docker image
- Start the Hublink Hypervisor service
The application will be available at http://localhost:8081 and will start automatically on boot.
- Docker and Docker Compose (installed by Hublink-Gateway-Setup)
- Hublink containers running from
/opt/hublinkdirectory (installed by Hublink-Gateway-Setup)
The setup script automatically:
- Stops any existing Hublink Hypervisor containers
- Removes the old installation directory
- Clones the latest configuration from GitHub
- Pulls the latest Docker image
- Starts the container with proper configuration
If you prefer to install manually:
-
Clone the repository:
sudo mkdir -p /opt/hublink-hypervisor sudo chown $(whoami):$(whoami) /opt/hublink-hypervisor cd /opt/hublink-hypervisor git clone https://github.com/Neurotech-Hub/Hublink-Hypervisor-Setup.git .
-
Pull the Docker image:
docker pull neurotechhub/hublink-hypervisor:latest
-
Start the container:
docker-compose up -d
The hypervisor uses the following configuration:
HUBLINK_PATH:/opt/hublink(path to Hublink containers)DOCKER_SOCKET:/var/run/docker.sock(Docker socket for container management)APP_PORT:8081(web interface port)
The docker-compose.yml file configures:
- Container name:
hublink-hypervisor - Network mode:
host(for direct access to host network) - Volumes: Docker socket and Hublink directory
- Restart policy:
always - Watchtower labels for automatic updates
docker ps | grep hublink-hypervisordocker logs -f hublink-hypervisorcd /opt/hublink-hypervisor
docker-compose downcd /opt/hublink-hypervisor
docker-compose up -dcd /opt/hublink-hypervisor
docker-compose restartOnce running, access the hypervisor at:
http://localhost:8081
The web interface provides:
- Real-time status monitoring of Hublink containers
- Container control (start/stop/restart)
- Internet connectivity monitoring
- Auto-fix capabilities for common issues
- Container logs viewing
- System health information
The container is configured for automatic updates via Watchtower. When a new version is pushed to Docker Hub, Watchtower will automatically:
- Pull the latest image
- Stop the current container
- Start a new container with the updated image
To manually update the container:
cd /opt/hublink-hypervisor
sudo git fetch origin
sudo git reset --hard origin/main
docker-compose down
docker-compose pull
docker-compose up -d-
Container not starting:
- Check Docker is running:
systemctl status docker - Check logs:
docker logs hublink-hypervisor - Verify Docker socket permissions
- Check Docker is running:
-
Cannot access web interface:
- Check container is running:
docker ps | grep hublink-hypervisor - Verify port 8081 is not in use:
lsof -i :8081 - Check firewall settings
- Check container is running:
-
Cannot access Hublink containers:
- Verify Hublink containers are running:
docker ps | grep hublink - Check
/opt/hublinkdirectory exists and has proper permissions - Ensure Hublink-Gateway-Setup was run first
- Verify Hublink containers are running:
-
Permission issues:
- Ensure user is in docker group:
groups $USER - Restart Docker service:
sudo systemctl restart docker - Log out and back in for group changes to take effect
- Ensure user is in docker group:
docker logs hublink-hypervisordocker logs --since "1h" hublink-hypervisordocker logs -f hublink-hypervisorFor additional support or to report issues, please visit: https://github.com/Neurotech-Hub/Hublink-Hypervisor-Setup/issues
This project is proprietary software for Hublink.cloud™.