Troubleshooting
Solutions for common issues with HYPR.Daemon Issues
Daemon Not Running
Symptom:Another Instance Running
Symptom:Permission Denied
Symptom:VM Issues
VM Fails to Start
Symptom:-
Missing kernel:
If missing, delete and let HYPR re-download:
-
KVM not available (Linux):
If missing, enable virtualization in BIOS or install KVM:
-
Hypervisor library not found (macOS):
Check if libkrun-efi is installed:
Install if missing:
VM Boot Timeout
Symptom:-
Image entrypoint fails immediately:
Check for application errors.
-
Resource constraints:
Increase memory:
- Slow disk I/O: Wait longer or check disk health.
Cannot Connect to VM Port
Symptom: Port mapping configured but connection refused. Checks:-
VM running:
-
Port mapping correct:
-
Service running in VM:
-
Firewall blocking:
Image Issues
Image Pull Failed
Symptom:-
Network connectivity:
-
DNS resolution:
-
Proxy settings:
If behind corporate proxy, set
HTTP_PROXYandHTTPS_PROXY.
Image Not Found
Symptom:-
Correct image name:
- Tag exists: Check registry for available tags.
- Architecture match: Some images only have x86_64 or ARM64 variants.
Build Failed
Symptom:- View build output: Build errors are printed to stdout.
-
Missing dependencies:
Add required packages in Dockerfile:
- Network in build: Build VMs have no network access. All downloads must happen in the base image or use multi-stage builds.
-
Check Dockerfile syntax:
Network Issues
No Network in VM
Symptom: VM cannot reach external networks. Linux checks:-
Bridge exists:
-
TAP attached:
-
IP forwarding enabled:
Enable:
-
NAT configured:
- vmnet service running: Check System Preferences > Sharing > Internet Sharing.
- libkrun permissions: May need to allow in Security & Privacy settings.
DNS Not Resolving
Symptom: VM cannot resolve hostnames. Inside VM:VMs Cannot Communicate
Symptom: VMs on same network cannot ping each other. Checks:- Same network: Ensure both VMs are on the same network (default or custom).
-
IP addresses:
-
Test connectivity:
Custom Network Not Working
Symptom: VMs on custom network cannot communicate. Checks:-
Network exists:
-
Network configuration:
-
VMs attached:
Check compose file has correct
networks:section.
Volume Issues
Volume Not Found
Symptom:-
List volumes:
-
Check name:
Stack volumes are prefixed:
<stack>_<volume> -
Check path:
Volume In Use
Symptom:-
Stop the VM:
-
Or force remove:
Permission Denied on Volume
Symptom: VM cannot read/write to volume. Checks:-
Host permissions:
-
Change permissions:
GPU Issues
GPU Not Detected (Linux)
Symptom:-
GPU present:
-
IOMMU enabled:
Add to kernel cmdline:
- Intel:
intel_iommu=on - AMD:
amd_iommu=on
- Intel:
-
VFIO modules:
Load:
GPU Passthrough Failed
Symptom:-
Unbind from current driver:
-
Bind to vfio-pci:
Metal Not Available (macOS)
Symptom: GPU option does nothing on Apple Silicon. Checks:- macOS version: Requires macOS 14 (Sonoma) or later.
-
libkrun-efi version:
Update:
brew upgrade libkrun-efi
Compose Issues
Stack Deploy Failed
Symptom:-
Compose file syntax:
-
Image availability:
- Port conflicts: Check if ports are already in use.
Service Dependency Timeout
Symptom: Service waits forever for dependency. Solution: Check if dependent service actually starts:Volumes Not Created
Symptom: Volume mount fails in compose. Checks:-
Volume defined:
Ensure volume is in top-level
volumes:section. -
Check volume:
Disk Space Issues
No Space Left
Symptom:-
Check usage:
-
Prune unused resources:
-
Prune volumes:
-
Remove specific images:
Debug Mode
Enable debug logging for detailed information:Getting Help
- Check logs:
journalctl -u hyprd -f(Linux) ortail -f /var/log/hypr/hyprd.log(macOS) - Enable debug logging:
RUST_LOG=debug - Check system resources:
hypr system df - Report issues: https://github.com/hyprhq/hypr/issues
Common Error Messages
| Error | Cause | Solution |
|---|---|---|
Failed to connect to daemon | Daemon not running | Start daemon with systemctl/launchctl |
Image not found | Image doesn’t exist | Check image name and registry |
VM health check timeout | VM failed to boot | Check logs, increase resources |
Port already in use | Port conflict | Use different port or stop conflicting service |
Volume in use | Volume attached to running VM | Stop VM or use —force |
Network in use | VMs attached to network | Remove VMs first or use —force |
No space left | Disk full | Run hypr system prune --all --volumes |