I found some other commands with same errors：

vyos@vyos:~$ update container image tailscale
-vbash: syntax error near unexpected token `then'

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

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.

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.

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

I did the same tests before updating this task, and it seemed like the code and build steps were fine.

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

Currently, I'm running:

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

I am running on VyOS 1.5-rolling-202503030030 , and this error has fixed

same issue on 1.5-rolling-202502130006

vyos@vyos# run show interfaces wireguard wg0
wg0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN group default qlen 1000
    link/none
    inet 10.10.0.1/24 brd 10.10.0.255 scope global wg0
       valid_lft forever preferred_lft forever
    inet6 fe80::f4d1:45ff:feb8:435/64 scope link
       valid_lft forever preferred_lft forever
    Description: hk wg over wss

I've also confirmed this problem exists on these versions:

I'm also facing the same issue: interfaces named pod-XXX vanish from the zone-based firewall after a system reboot. Here's my configuration:

vyos@vyos# sudo ip netns list
netns-3ea94443-cb81-9ea7-05a1-d1e08b1cafe8 (id: 0)

Based on your suggestion, I submitted a PR to accept the traffic for the PPPoE session. However,I'm not sure how to accept these STP traffic , so the STP was not included.

Nov 27 21:47:20 kernel: [STATE-POLICY-INV-A]IN= OUT=eth3 MAC=01:80:c2:00:00:00:60:be:b4:10:7a:6d:00:26
Nov 27 21:47:20 kernel: [STATE-POLICY-INV-A]IN= OUT=eth2 MAC=01:80:c2:00:00:00:60:be:b4:10:7a:6c:00:26

21:35:57.958675 60:be:b4:10:7a:6a > 01:80:c2:00:00:00, 802.3, length 38: LLC, dsap STP (0x42) Individual, ssap STP (0x42) Command, ctrl 0x03: STP 802.1d, Config, Flags [none], bridge-id 8000.52:37:9c:d2:22:eb.8001, length 35

this isthe invalid stp traffic log

Hi @n.fort
the error messages disappeared after manual add your command. there still has few stp traffic with same error

Thank you for your work. I tried upgrading to the latest version 1.5-rolling-202411220007. After the upgrade, I still lost access to the LAN. However, after checking the logs, it seems that the previous exception has been fixed. There are just a few logs: Sending reply: error_code 1 with output. I'm not sure if this is a bug; could you please take a look?

I am sorry I just found another task with same issue, https://vyos.dev/T6770, Please close this task.

@Ironeagle My solution is adding this command:

I am facing same issue here.
In my case, My laptop hostname is cn002472.xxx.com