Fix Karakeep Chrome connectivity on PD
This commit is contained in:
@@ -73,7 +73,9 @@ services:
|
|||||||
NEXTAUTH_SECRET: ${KARAKEEP_NEXTAUTH_SECRET}
|
NEXTAUTH_SECRET: ${KARAKEEP_NEXTAUTH_SECRET}
|
||||||
MEILI_ADDR: http://karakeep-meilisearch:7700
|
MEILI_ADDR: http://karakeep-meilisearch:7700
|
||||||
MEILI_MASTER_KEY: ${KARAKEEP_MEILI_MASTER_KEY}
|
MEILI_MASTER_KEY: ${KARAKEEP_MEILI_MASTER_KEY}
|
||||||
BROWSER_WEB_URL: http://karakeep-chrome:9222
|
# Chromium remote debugging now rejects non-local hostname Host headers here,
|
||||||
|
# so Karakeep must reach Chrome over a stable bridge IP rather than service DNS.
|
||||||
|
BROWSER_WEB_URL: http://172.16.16.3:9222
|
||||||
DISABLE_SIGNUPS: ${KARAKEEP_DISABLE_SIGNUPS}
|
DISABLE_SIGNUPS: ${KARAKEEP_DISABLE_SIGNUPS}
|
||||||
DB_WAL_MODE: ${KARAKEEP_DB_WAL_MODE}
|
DB_WAL_MODE: ${KARAKEEP_DB_WAL_MODE}
|
||||||
LOG_LEVEL: ${KARAKEEP_LOG_LEVEL}
|
LOG_LEVEL: ${KARAKEEP_LOG_LEVEL}
|
||||||
@@ -102,7 +104,8 @@ services:
|
|||||||
- --remote-debugging-port=9222
|
- --remote-debugging-port=9222
|
||||||
- --hide-scrollbars
|
- --hide-scrollbars
|
||||||
networks:
|
networks:
|
||||||
- karakeep
|
karakeep:
|
||||||
|
ipv4_address: 172.16.16.3
|
||||||
|
|
||||||
karakeep-meilisearch:
|
karakeep-meilisearch:
|
||||||
image: getmeili/meilisearch:v1.41.0
|
image: getmeili/meilisearch:v1.41.0
|
||||||
@@ -126,3 +129,10 @@ networks:
|
|||||||
external: true
|
external: true
|
||||||
karakeep:
|
karakeep:
|
||||||
name: documents_karakeep
|
name: documents_karakeep
|
||||||
|
# Pin the subnet so karakeep-chrome keeps the IP Karakeep uses for DevTools.
|
||||||
|
ipam:
|
||||||
|
config:
|
||||||
|
- subnet: 172.16.16.0/24
|
||||||
|
gateway: 172.16.16.1
|
||||||
|
- subnet: fdd0:0:0:10::/64
|
||||||
|
gateway: fdd0:0:0:10::1
|
||||||
|
|||||||
Reference in New Issue
Block a user