Repository navigation
Expand file tree
/
Copy pathdocker-compose.arr-stack.yml
More file actions
607 lines (587 loc) · 26.6 KB
/
Copy pathdocker-compose.arr-stack.yml
File metadata and controls
607 lines (587 loc) · 26.6 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
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
#####################################################################
# ⚠️ NEVER use 'docker compose down' - kills Pi-hole DNS! #
# ⚠️ You WILL lose internet before you can run 'up -d' #
# #
# ✅ Safe restart: docker compose -f docker-compose.arr-stack.yml up -d --force-recreate
# ✅ Or use: ./scripts/restart-stack.sh #
#####################################################################
#########################
# Centralized Volumes #
#########################
# The explicit `name:` on every volume pins it to the physical volume that
# already exists. Do not remove them, and do not "tidy" them to match a new
# project name.
#
# A volume declared without `name:` is scoped by the Compose project name.
# Before the project name was pinned below, that name was derived from the
# deploy directory — the physical volumes are called arr-stack_<volume>
# purely because the directory happened to be named arr-stack — and a
# renamed directory made Compose silently create brand-new EMPTY volumes
# and start every container against them, all reporting healthy with their
# config gone. Pinning the volume names decouples the data from both the
# directory and the project name, so neither rename can strand it.
#
# The project name is pinned too, and shared with docker-compose.traefik.yml
# and docker-compose.utilities.yml on purpose: the three files are one
# project, which is why `--remove-orphans` on any of them deletes the
# others' containers (CLAUDE.md). tests/compose-validation.bats holds the
# expected names. To keep a different project name on an existing deploy,
# set COMPOSE_PROJECT_NAME in .env — the environment overrides this key.
name: arr-stack
volumes:
gluetun-config:
name: arr-stack_gluetun-config
qbittorrent-config:
name: arr-stack_qbittorrent-config
sabnzbd-config:
name: arr-stack_sabnzbd-config
sonarr-config:
name: arr-stack_sonarr-config
prowlarr-config:
name: arr-stack_prowlarr-config
radarr-config:
name: arr-stack_radarr-config
jellyfin-config:
name: arr-stack_jellyfin-config
jellyfin-cache:
name: arr-stack_jellyfin-cache
seerr-config:
name: arr-stack_seerr-config
bazarr-config:
name: arr-stack_bazarr-config
dnscrypt-config:
name: arr-stack_dnscrypt-config
pihole-etc-pihole:
name: arr-stack_pihole-etc-pihole
#########################
# Networks #
#########################
networks:
vpn-net:
driver: bridge
ipam:
config:
- subnet: 10.8.1.0/24
arr-stack:
name: arr-stack
driver: bridge
ipam:
config:
- subnet: 172.20.0.0/24
ip_range: 172.20.0.128/25
gateway: 172.20.0.1
#########################
# Logging #
#########################
x-logging: &default-logging
driver: "json-file"
options:
max-size: "10m"
max-file: "3"
#########################
# Security Defaults #
#########################
x-security: &default-security
security_opt:
- no-new-privileges:true
cap_drop:
- ALL
# LinuxServer.io images use s6-overlay which needs CHOWN/SETUID/SETGID/DAC_OVERRIDE
# to switch users during init. Extend default-security with these caps.
x-security-lsio: &lsio-security
security_opt:
- no-new-privileges:true
cap_drop:
- ALL
cap_add:
- CHOWN
- SETUID
- SETGID
- DAC_OVERRIDE
#########################
# Services #
#########################
services:
# ═══════════════════════════════════════════════════════════════════════════
# GLUETUN - VPN gateway. Routes download traffic through your VPN provider.
# All services below marked "via VPN" share this network for privacy.
# ═══════════════════════════════════════════════════════════════════════════
gluetun:
image: qmcgaw/gluetun:v3.41
container_name: gluetun
<<: *default-security
depends_on:
pihole:
condition: service_healthy # Wait for Pi-hole DNS before VPN connects
cap_add:
- NET_ADMIN
# gluetun runs as uid 0, but `cap_drop: ALL` above also takes away caps
# the default Docker set would have handed it. It needs these back:
#
# CHOWN - gluetun chowns /etc/openvpn/target.ovpn. Only the
# OpenVPN path touches it, so VPN_TYPE=wireguard never
# notices, but VPN_TYPE=openvpn fails 100% of the time
# with "chown /etc/openvpn/target.ovpn: operation not
# permitted" and retries forever.
# DAC_OVERRIDE - without it, root is subject to normal file permissions.
# OpenVPN then can't read back the file it just chowned
# away from itself ("--auth-user-pass fails with
# '/etc/openvpn/auth.conf': Permission denied"), and on
# EVERY VPN type gluetun can't write /tmp/gluetun/ip, so
# /v1/publicip/ip silently returns "" and the log fills
# with "clearing public IP data: permission denied".
#
# Adding NET_ADMIN alone looks right because every gluetun guide says
# that's all you need - true only because they don't drop the default caps.
- CHOWN
- DAC_OVERRIDE
# SETUID - OpenVPN drops privileges to `nonrootuser` once the
# tunnel is up. gluetun writes `user nonrootuser` into
# target.ovpn unconditionally -- including when its own
# settings summary says "Run OpenVPN as: root", and even
# with OPENVPN_PROCESS_USER=root set -- so the setuid is
# not avoidable by configuration. Without this cap:
# "setuid('nonrootuser') failed: Operation not permitted
# (errno=1)" AFTER the tunnel establishes, so the peer
# connects and the link comes up before it dies.
# SETGID is deliberately NOT here: gluetun writes no
# `group` directive, and the tunnel completes without it.
- SETUID
devices:
- /dev/net/tun:/dev/net/tun
volumes:
- gluetun-config:/gluetun
environment:
# VPN Configuration - see .env.example for provider-specific setup
- VPN_SERVICE_PROVIDER=${VPN_SERVICE_PROVIDER}
- VPN_TYPE=${VPN_TYPE}
- WIREGUARD_PRIVATE_KEY=${WIREGUARD_PRIVATE_KEY}
- WIREGUARD_ADDRESSES=${WIREGUARD_ADDRESSES}
- SERVER_COUNTRIES=${VPN_COUNTRIES}
- TZ=${TZ}
- DNS_ADDRESS=172.20.0.5
# Health check targets, deliberately IP:port and not hostnames.
#
# DNS_ADDRESS above disables gluetun's own resolver (it says so at every
# startup), making Pi-hole a hard dependency for all DNS. gluetun's
# default health targets are `github.com:443,cloudflare.com:443` — NAMES.
# So the check that decides whether the VPN is alive was being answered
# by Pi-hole, and a Pi-hole wobble was indistinguishable from a dead
# tunnel. gluetun's response is to rebuild the tunnel, which cannot fix
# DNS, so it loops — taking every VPN-side container's network with it on
# each pass, and never recovering on its own.
#
# On 2026-08-05 that produced 323 VPN rebuilds and 10 container restarts
# between 19:32 and 21:18. Pi-hole's own query log for the window shows
# it flapping rather than dead — multi-minute gaps, and 17 minutes at
# 2 queries/min against a 20–150/min baseline — and gluetun's restart
# clusters line up with the gaps. It stopped only when the container was
# restarted by hand.
#
# These addresses take DNS out of the decision entirely: the check now
# tests the tunnel and nothing else. DNS is still checked, but by
# scripts/check-vpn.sh, where failing means being told about it rather
# than having the VPN torn down in response.
- HEALTH_TARGET_ADDRESSES=1.1.1.1:443,8.8.8.8:443
- FIREWALL_OUTBOUND_SUBNETS=${LAN_SUBNET},172.20.0.0/24,10.8.1.0/24
ports:
# Ports for services using network_mode: "service:gluetun"
# Enables direct local access without Traefik (http://NAS_IP:PORT)
# NOTE: Sonarr (8989) & Radarr (7878) now run on the arr-stack bridge
# (their own static IPs) and publish their own ports — see those services.
- "9696:9696" # Prowlarr
- "8085:8085" # qBittorrent
- "8082:8080" # SABnzbd
- "8191:8191" # FlareSolverr
networks:
arr-stack:
ipv4_address: 172.20.0.3
vpn-net:
restart: always
logging: *default-logging
healthcheck:
test: ["CMD", "/gluetun-entrypoint", "healthcheck"]
interval: 1m
timeout: 10s
retries: 3
start_period: 30s # Give VPN time to establish connection
# ═══════════════════════════════════════════════════════════════════════════
# QBITTORRENT - Torrent download client. Downloads files through VPN.
# Access: qbit.lan | qbit.yourdomain.com | NAS_IP:8085
# ═══════════════════════════════════════════════════════════════════════════
qbittorrent:
image: lscr.io/linuxserver/qbittorrent:5.3.0
container_name: qbittorrent
<<: *lsio-security
network_mode: "service:gluetun"
depends_on:
gluetun:
condition: service_healthy
restart: true
environment:
- PUID=${PUID}
- PGID=${PGID}
- TZ=${TZ}
- WEBUI_PORT=8085
- DOCKER_MODS=ghcr.io/vuetorrent/vuetorrent-lsio-mod:latest
volumes:
- qbittorrent-config:/config
- ${MEDIA_ROOT}:/data
# Re-pins BitTorrent traffic to gluetun's tun0 and keeps it pinned. Without
# it, a rebuilt config volume loses the binding and every torrent silently
# stalls at metaDL. See docs/TROUBLESHOOTING.md.
- ./qbittorrent/custom-services.d:/custom-services.d:ro
labels:
- deunhealth.restart.on.unhealthy=true
- gluetun.dependent=true # gluetun-recover restarts this if SIGKILLed by a gluetun restart
restart: always
logging: *default-logging
healthcheck:
test: ["CMD-SHELL", "curl -sf http://localhost:8085/ && wget -q --spider --timeout=5 http://www.google.com"]
interval: 2m
timeout: 15s
retries: 4
start_period: 60s
# ═══════════════════════════════════════════════════════════════════════════
# SABNZBD - Usenet download client. Downloads via VPN for extra security.
# Access: sabnzbd.lan | sabnzbd.yourdomain.com | NAS_IP:8082
# ═══════════════════════════════════════════════════════════════════════════
sabnzbd:
image: lscr.io/linuxserver/sabnzbd:5.1.3
container_name: sabnzbd
<<: *lsio-security
network_mode: "service:gluetun"
depends_on:
gluetun:
condition: service_healthy
restart: true
environment:
- PUID=${PUID}
- PGID=${PGID}
- TZ=${TZ}
volumes:
- sabnzbd-config:/config
- ${MEDIA_ROOT}:/data
labels:
- deunhealth.restart.on.unhealthy=true
- gluetun.dependent=true # gluetun-recover restarts this if SIGKILLed by a gluetun restart
restart: always
logging: *default-logging
healthcheck:
test: ["CMD-SHELL", "curl -sf http://localhost:8080/ && wget -q --spider --timeout=5 http://www.google.com"]
interval: 3m
timeout: 15s
retries: 4
start_period: 60s
# ═══════════════════════════════════════════════════════════════════════════
# SONARR - TV show monitor. Watches for new episodes and sends to download.
# Access: sonarr.lan | sonarr.yourdomain.com | NAS_IP:8989
# Runs on the arr-stack bridge (own IP 172.20.0.10), NOT behind the VPN:
# Sonarr only talks to metadata providers (TVDB/TMDB) + internal services,
# never to indexers/peers, so it needs no VPN. Staying on the bridge means a
# gluetun/VPN reconnect no longer cuts Sonarr off from Seerr/Bazarr.
# It reaches the VPN-side download clients via the `gluetun` hostname.
# ═══════════════════════════════════════════════════════════════════════════
sonarr:
image: lscr.io/linuxserver/sonarr:4.0.20
container_name: sonarr
<<: *lsio-security
environment:
- PUID=${PUID}
- PGID=${PGID}
- TZ=${TZ}
ports:
- "8989:8989" # Direct local access (http://NAS_IP:8989)
networks:
arr-stack:
ipv4_address: 172.20.0.10
volumes:
- sonarr-config:/config
- ${MEDIA_ROOT}:/data
labels:
- deunhealth.restart.on.unhealthy=true
restart: always
logging: *default-logging
healthcheck:
test: ["CMD", "curl", "-sf", "http://localhost:8989/"]
interval: 2m
timeout: 15s
retries: 3
start_period: 60s
# ═══════════════════════════════════════════════════════════════════════════
# PROWLARR - Indexer manager. Finds download sources for Sonarr/Radarr.
# Access: prowlarr.lan | prowlarr.yourdomain.com | NAS_IP:9696
# ═══════════════════════════════════════════════════════════════════════════
prowlarr:
image: lscr.io/linuxserver/prowlarr:2.6.5
container_name: prowlarr
<<: *lsio-security
network_mode: "service:gluetun"
depends_on:
gluetun:
condition: service_healthy
restart: true
environment:
- PUID=${PUID}
- PGID=${PGID}
- TZ=${TZ}
volumes:
- prowlarr-config:/config
labels:
- deunhealth.restart.on.unhealthy=true
- gluetun.dependent=true # gluetun-recover restarts this if SIGKILLed by a gluetun restart
restart: always
logging: *default-logging
healthcheck:
test: ["CMD", "curl", "-sf", "http://localhost:9696/"]
interval: 2m
timeout: 15s
retries: 3
start_period: 60s
# ═══════════════════════════════════════════════════════════════════════════
# RADARR - Movie monitor. Watches for new movies and sends to download.
# Access: radarr.lan | radarr.yourdomain.com | NAS_IP:7878
# Runs on the arr-stack bridge (own IP 172.20.0.11), NOT behind the VPN —
# same rationale as Sonarr above. Reaches VPN-side download clients via the
# `gluetun` hostname.
# ═══════════════════════════════════════════════════════════════════════════
radarr:
image: lscr.io/linuxserver/radarr:6.4.4
container_name: radarr
<<: *lsio-security
environment:
- PUID=${PUID}
- PGID=${PGID}
- TZ=${TZ}
ports:
- "7878:7878" # Direct local access (http://NAS_IP:7878)
networks:
arr-stack:
ipv4_address: 172.20.0.11
volumes:
- radarr-config:/config
- ${MEDIA_ROOT}:/data
labels:
- deunhealth.restart.on.unhealthy=true
restart: always
logging: *default-logging
healthcheck:
test: ["CMD", "curl", "-sf", "http://localhost:7878/"]
interval: 2m
timeout: 15s
retries: 3
start_period: 60s
# ═══════════════════════════════════════════════════════════════════════════
# JELLYFIN - Media server. Stream your movies and TV shows like Netflix.
# Access: jellyfin.lan | jellyfin.yourdomain.com | NAS_IP:8096
# ═══════════════════════════════════════════════════════════════════════════
jellyfin:
image: jellyfin/jellyfin:12.3
container_name: jellyfin
<<: *default-security
cap_add:
- CHOWN # Create config/cache subdirs on first run
- DAC_OVERRIDE # Write to root-owned volume directories
ports:
- "8096:8096" # Web UI
- "7359:7359/udp" # Client discovery (auto-detect on LAN)
- "1900:1900/udp" # DLNA
environment:
- TZ=${TZ}
# Hardware transcoding (Intel Quick Sync) - remove these 4 lines if no Intel GPU
devices:
- /dev/dri:/dev/dri
group_add:
- "${RENDER_GROUP_ID:-0}" # Find ID: getent group render | cut -d: -f3
volumes:
- jellyfin-config:/config
- jellyfin-cache:/cache
# The whole data root, read-only, so a Books library can index the
# `other` download lane (/data/usenet/complete/other, /data/torrents/other)
# as well as /data/media. Library paths under /data/media are unchanged.
- ${MEDIA_ROOT}:/data:ro
networks:
arr-stack:
ipv4_address: 172.20.0.4
restart: always
logging: *default-logging
healthcheck:
test: ["CMD", "curl", "-f", "http://localhost:8096/health"]
interval: 1m
timeout: 30s
retries: 2
start_period: 30s
# ═══════════════════════════════════════════════════════════════════════════
# DNSCRYPT-PROXY - DNS over HTTPS/DNSCrypt proxy. Encrypts DNS queries.
# No web UI. Used internally by Pi-hole at 172.20.0.6:5053
# Protocols: DoH (DNS over HTTPS), DNSCrypt, Anonymized DNS
# Config: dnscrypt-proxy/dnscrypt-proxy.toml (the image default, plus a denylist of DNS64 resolvers)
# ═══════════════════════════════════════════════════════════════════════════
dnscrypt-proxy:
image: klutchell/dnscrypt-proxy:2.1.20
container_name: dnscrypt-proxy
cap_drop:
- ALL
security_opt:
- no-new-privileges:true
group_add:
- "${PGID}" # the toml below is read from the checkout; a NAS share that admits only its own accounts (UGOS does) refuses the image's uid 65532 without a group it knows
networks:
arr-stack:
ipv4_address: 172.20.0.6
volumes:
- dnscrypt-config:/config # resolver-list cache (public-resolvers.md, relays.md, .minisig)
- ./dnscrypt-proxy/dnscrypt-proxy.toml:/config/dnscrypt-proxy.toml:ro # the file only: the volume keeps the cache beside it
environment:
- TZ=${TZ}
restart: always
logging: *default-logging
healthcheck:
test: ["CMD", "/usr/local/bin/dnsprobe", "google.com", "127.0.0.1:5053"]
interval: 30s
timeout: 10s
retries: 2
start_period: 30s
# ═══════════════════════════════════════════════════════════════════════════
# PI-HOLE - DNS server. Enables .lan domains and blocks ads network-wide.
# Access: pihole.lan/admin | NAS_IP:8081/admin
# For: Home Pro + Anywhere setups
# Configure upstream DNS: Settings → DNS → Custom = 172.20.0.6#5053
# ═══════════════════════════════════════════════════════════════════════════
pihole:
image: pihole/pihole:2026.10.0
container_name: pihole
depends_on:
dnscrypt-proxy:
condition: service_healthy
ports:
- "${NAS_IP}:53:53/tcp" # Bind to NAS IP (not 0.0.0.0) to avoid conflict with host dnsmasq on 127.0.0.1:53
- "${NAS_IP}:53:53/udp" # NAS_IP MUST be a static IP — DHCP IPs aren't ready at boot, causing exit 128
- "8081:80" # Web UI (local network access)
networks:
arr-stack:
ipv4_address: 172.20.0.5
environment:
- TZ=${TZ}
- FTLCONF_webserver_api_password=${PIHOLE_UI_PASS}
- FTLCONF_dns_listeningMode=all
- FTLCONF_misc_etc_dnsmasq_d=true
volumes:
- pihole-etc-pihole:/etc/pihole
- ./pihole/dnsmasq.d:/etc/dnsmasq.d
security_opt:
- no-new-privileges:false # Pi-hole FTL needs setcap to apply capabilities
cap_drop:
- ALL
cap_add:
- CHOWN # File ownership during startup
- NET_ADMIN # DNS server binding
- NET_RAW # Raw socket access for DHCP/DNS
- SYS_NICE # Priority scheduling for FTL
- SETUID # Drop privileges after startup
- SETGID # Drop privileges after startup
- SETFCAP # Apply capabilities to FTL binary
- DAC_OVERRIDE # Access config files during startup
restart: always
logging: *default-logging
healthcheck:
test: ["CMD", "dig", "@127.0.0.1", "-p", "53", "google.com", "+short"]
interval: 30s
timeout: 10s
retries: 2
start_period: 30s
# ═══════════════════════════════════════════════════════════════════════════
# SEERR (formerly Jellyseerr) - Request portal. Users request movies/shows here.
# Access: seerr.lan | seerr.yourdomain.com | NAS_IP:5055
# ═══════════════════════════════════════════════════════════════════════════
seerr:
image: ghcr.io/seerr-team/seerr:v3.5.1
init: true
container_name: seerr
# No cap_add: the image runs as node (UID 1000), and a non-root process
# gets no effective capabilities from cap_add. Docker copies the image's
# node-owned /app/config into a new volume, so Seerr can write it anyway.
<<: *default-security
ports:
- "5055:5055"
environment:
- LOG_LEVEL=info
- TZ=${TZ}
- PORT=5055
networks:
arr-stack:
ipv4_address: 172.20.0.8
volumes:
- seerr-config:/app/config
# Seerr shows "/app/config volume mount was not configured properly" while
# /app/config/DOCKER exists. The image ships that marker so a missing mount
# gets noticed, but Docker copies image contents into a new named volume,
# marker included, so every fresh install saw the warning. The data does
# persist. Delete the marker on start; `npm start` is the image's own CMD.
command: ["sh", "-c", "rm -f /app/config/DOCKER && exec npm start"]
restart: always
logging: *default-logging
healthcheck:
test: ["CMD", "wget", "--no-verbose", "--tries=1", "--spider", "http://localhost:5055/api/v1/status"]
interval: 2m
timeout: 10s
retries: 3
start_period: 20s
# ═══════════════════════════════════════════════════════════════════════════
# BAZARR - Subtitle manager. Automatically downloads subtitles.
# Access: bazarr.lan | bazarr.yourdomain.com | NAS_IP:6767
# ═══════════════════════════════════════════════════════════════════════════
bazarr:
image: lscr.io/linuxserver/bazarr:1.6.2
container_name: bazarr
<<: *lsio-security
ports:
- "6767:6767"
environment:
- PUID=${PUID}
- PGID=${PGID}
- TZ=${TZ}
networks:
arr-stack:
ipv4_address: 172.20.0.9
volumes:
- bazarr-config:/config
- ${MEDIA_ROOT}/media:/data/media
restart: always
logging: *default-logging
healthcheck:
test: ["CMD", "curl", "-f", "http://localhost:6767/"]
interval: 3m
timeout: 10s
retries: 2
start_period: 60s
# ═══════════════════════════════════════════════════════════════════════════
# FLARESOLVERR - Cloudflare bypass. Helps Prowlarr access protected sites.
# Runs behind Gluetun VPN so solved cookies match Prowlarr's exit IP.
# No web UI. Used internally by Prowlarr at localhost:8191
# ═══════════════════════════════════════════════════════════════════════════
flaresolverr:
image: ghcr.io/flaresolverr/flaresolverr:v3.5.2
container_name: flaresolverr
<<: *default-security
network_mode: "service:gluetun"
depends_on:
gluetun:
condition: service_healthy
environment:
- LOG_LEVEL=info
- TZ=${TZ}
labels:
- deunhealth.restart.on.unhealthy=true
- gluetun.dependent=true # gluetun-recover restarts this if SIGKILLed by a gluetun restart
restart: always
logging: *default-logging
healthcheck:
# Actually test Chrome by making a solve request (catches Chrome crashes)
test: ["CMD", "curl", "-sf", "-X", "POST", "-H", "Content-Type: application/json",
"-d", "{\"cmd\":\"request.get\",\"url\":\"http://localhost:8191/\",\"maxTimeout\":30000}",
"http://localhost:8191/v1"]
interval: 10m
timeout: 60s
retries: 2
start_period: 60s