It seems to be broken once again - at least for devices <=1G RAM.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Aug 26 2024
Aug 25 2024
Aug 24 2024
Aug 23 2024
I messed around with it today, and made some progress!
A simple version of get_commit_scripts (nee get_commit_schedule) has been added to the resolution of T6671. After that PR is merged, this task will be closed, as that version suffices for current needs.
The following simple commit will need to be backported to sagitta so that a PR for the above will backport cleanly:
https://github.com/vyos/vyos-1x/pull/4013
I think we can close this one
Only worked:
- Reboot instance
- load /config/config.boot
- sudo podman rm suricata
- commit
Then it works
vyos@VyOS-Test01# [edit] vyos@VyOS-Test01# load /config/config.boot [edit] vyos@VyOS-Test01# [edit] vyos@VyOS-Test01# compare + container { + name suricata { + allow-host-networks + arguments "-q 1" + capability "net-admin" + capability "sys-admin" + capability "sys-nice" + image "jasonish/suricata:6.0.14" + memory "1024" + volume ETC { + destination "/etc/suricata" + source "/config/suricata/etc" + } + volume LOGS { + destination "/var/log/suricata" + source "/config/suricata/logs" + } + volume RULES { + destination "/var/lib/suricata/rules/" + source "/config/suricata/rules" + } + } + }
If service is 'failed' state
vyos@VyOS-Test01:~$ systemctl status vyos-container-suricata.service × vyos-container-suricata.service - VyOS Container suricata Loaded: loaded (/run/systemd/system/vyos-container-suricata.service; static) Active: failed (Result: exit-code) since Fri 2024-08-23 10:32:44 UTC; 43s ago Duration: 4min 55.702s Process: 2855 ExecStartPre=/bin/rm -f /run/vyos-container-suricata.service.pid /run/vyos-container-suricata.service.cid (code=exited, sta> Process: 2856 ExecStart=/usr/bin/podman run --conmon-pidfile /run/vyos-container-suricata.service.pid --cidfile /run/vyos-container-suric> Process: 2867 ExecStopPost=/usr/bin/podman rm --ignore -f --cidfile /run/vyos-container-suricata.service.cid (code=exited, status=0/SUCCE> Process: 2873 ExecStopPost=/bin/rm -f /run/vyos-container-suricata.service.cid (code=exited, status=0/SUCCESS) CPU: 129ms
In T6673#198344, @a.hajiyev wrote:You are right there is an op-mode command to restart the container
restart container suricataBut I think there needs to be some checks/changes at least someone will execute the native Podman command to restart the container.
You are right there is an op-mode command to restart the container
restart container suricata
But I think there needs to be some checks/changes at least someone will execute the native Podman command to restart the container.
Sorry, but that was my own mistake. When I checked again today, I noticed that the connections were not allowed in the firewall.
It fails because you do it in the wrong way
PR to follow smoketests and cosmetic changes:
https://github.com/vyos/vyos-1x/compare/current...jestabro:configdep-prio