dustin
/
configpolicy
1
1
Fork 0
Code Issues Releases Activity

r/v-l: Use the host network 

I don't know what the deal is, but restarting the _victoria-logs_
container makes it lose inbound network connectivity.  It appears that
the firewall rules that forward the ports to the container's namespace
seem to get lost, but I can't figure out why.  To fix it, I have to
flush the netfilter rules (`nft flush ruleset`) and then restart
_firewalld_ and _victoria-logs_ to recreate them.  This is rather
cumbersome, and since Victoria Logs runs on a dedicated VM, there's
really not much advantage to isolating the container's network.
unifi-restore
Dustin 2025-07-27 12:49:24 -05:00
parent b2d35ac881
commit 59d17bf3f4
1 changed files with 1 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
roles/victoria-logs/templates/victoria-logs.container.j2
View File

@ -16,10 +16,7 @@ NoNewPrivileges=yes
ReadOnly=yes ReadOnly=yes
ReadOnlyTmpfs=yes ReadOnlyTmpfs=yes
AddCapability=CAP_NET_BIND_SERVICE AddCapability=CAP_NET_BIND_SERVICE
PublishPort=9428:9428 Network=host
{% for portspec in victoria_logs_publish_ports %}
PublishPort={{ portspec }}
{% endfor %}
HealthCmd=/usr/bin/wget -q -O /dev/null 127.0.0.1:9428/health HealthCmd=/usr/bin/wget -q -O /dev/null 127.0.0.1:9428/health
HealthInterval=1m HealthInterval=1m
HealthOnFailure=stop HealthOnFailure=stop