-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathdocker-compose.arcane.gpu.yml
More file actions
32 lines (32 loc) · 1.34 KB
/
Copy pathdocker-compose.arcane.gpu.yml
File metadata and controls
32 lines (32 loc) · 1.34 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
# honeypot-arcane — GPU-monitoring overlay (#2950).
#
# Arcane's GPU panel needs an NVIDIA device reserved for the container. That
# reservation is a HARD requirement: Docker refuses to start the container at
# all when no nvidia device driver is present —
#
# Error response from daemon: could not select device driver "nvidia" with capabilities: [[gpu]]
#
# — and `count: 0` does not soften it (measured on a driverless host: both
# `count: all` and `count: 0` fail identically). Since Arcane is the control
# plane that materializes every other stack via its gitops syncs, having that
# requirement in the base file meant one optional monitoring panel could take
# out the entire install on a host whose GPU driver was not up yet. That is
# exactly what happened on the 2026-09-03 Rocky 10 rebuild.
#
# So the base docker-compose.arcane.yml is GPU-free and always startable, and
# install-homeserver.sh merges this overlay into the rendered compose.yml only
# after it has confirmed a working NVIDIA runtime on the host. Nothing here is
# required for Arcane to manage stacks.
services:
arcane:
environment:
GPU_MONITORING_ENABLED: "true"
GPU_TYPE: nvidia
NVIDIA_VISIBLE_DEVICES: all
deploy:
resources:
reservations:
devices:
- driver: nvidia
count: all
capabilities: [gpu]