feat: manage vector container via compose
Using compose instead of manual docker calls allows folks to customize the vector container by using a custom compose.yml template file. This opens us up to more customizations while aligning container management with how we do other external containers (such as for the proxy plugins). Refs #5784
This commit is contained in:
25
plugins/logs/templates/compose.yml.tmpl
Normal file
25
plugins/logs/templates/compose.yml.tmpl
Normal file
@@ -0,0 +1,25 @@
|
||||
---
|
||||
version: "3.7"
|
||||
|
||||
services:
|
||||
vector:
|
||||
image: "{{ $.VectorImage }}"
|
||||
|
||||
command:
|
||||
- "--config"
|
||||
- "/etc/vector/vector.json"
|
||||
- "--watch-config"
|
||||
|
||||
labels:
|
||||
dokku: ""
|
||||
org.label-schema.schema-version: "1.0"
|
||||
org.label-schema.vendor: dokku
|
||||
|
||||
network_mode: bridge
|
||||
|
||||
restart: unless-stopped
|
||||
|
||||
volumes:
|
||||
- "{{ $.DokkuLibRoot }}/data/logs:/etc/vector"
|
||||
- "/var/run/docker.sock:/var/run/docker.sock:ro"
|
||||
- "{{ $.DokkuLogsDir }}/apps:/var/log/dokku/apps"
|
||||
Reference in New Issue
Block a user