https://github.com/vyos/vyos-1x/pull/4528

PR
https://github.com/vyos/vyos-build/pull/968
https://github.com/vyos/vyos-build/pull/969

See T7220 and T7214, also PR https://github.com/vyos/vyos-1x/pull/4469

PR: https://github.com/vyos/vyos-build/pull/967

Sure, but leaving the option to configure it globally does not take away the option to configure it per container.

I understand the preference for global configuration. While that approach can be simple and convenient.
However, I had a bad experience where a container started spamming logs because of network problems, and it filled up the whole disk (200GB) in just one hour. That broke many stuff on my VyOS.

Personally I'd rather configure it globally instead for each container.
Also not that Podman 5 will change the default to journald.

In this PR I have refactored the log driver code to allow it to be configured per container. In addition to k8s-file and journald, a none option was added to disable logging.

Tested. It works

I created a task for this as well https://vyos.dev/T7469

Will it not do what you want?

set firewall ipv4 prerouting raw default-action 'accept'
set firewall ipv4 prerouting raw rule 10 action 'notrack'
set firewall ipv4 prerouting raw rule 10 source address '192.0.2.0/24'

@L0crian @a.apostoliuk @sarthurdev I think I agree with the idea to add an option to disable conntrack per chain. I made a task about that: T7475

@Fabse That field is for the compatibility implications of the change for the purpose of backport decisions and release notes. This is a bug, so a fix that restores correct behavior has no compatibility implications — it will just make the system work as it was always expected to work, so it will be safe to backport to any releases and will not require the user to take any action.

PR: https://github.com/vyos/vyos-1x/pull/4524

add a warning for 1.4 https://github.com/VyOS-Networks/vyos-1x/pull/722

PR: https://github.com/vyos/vyos-1x/pull/4522

https://github.com/vyos/vyos-1x/pull/4521