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

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

@Viacheslav I'd suggest to reopen this issue.

Blackbox exporter requires a config file for modules that should be used (for example ping over IPv4 or IPv6, DNS for A or AAAA).

This feature is missing documentation: https://docs.vyos.io/en/latest/configuration/service/monitoring.html

Yes, I linked the article for background why the MTU setting is helpful, this applies to Podman as well as Docker.

In July Podman was upgraded from 4.3 (debian package) to 4.9 (custom built package)

@Viacheslav I think this can be closed, I'm not aware of open issues regarding this.

will you add podman exporter as well?

I got the drivers and vyos image built.
One thing I noticed some of the tools require mft to also be installed (https://network.nvidia.com/products/adapter-software/firmware-tools/).

@Viacheslav I can try testing this on my test bench as I have a couple of spare ConnectX 4/5 to play around. Is this in 1.5 rolling?

This task has been completed with https://github.com/vyos/vyos-documentation/pull/1548

Thanks for verifying. Interesting, is it also using the custom Podman package?

@c-po To me it looks like the custom package from T6598 does not install the policy.json

Verified on my 1.4 install the policy.json is present, but missing in the latest rolling release

@Viacheslav Fabse started working on it and I did have a look at the changes last week.

I would have put it on my list. @Fabse if you get stuck or need some support just slack me.

Relevant telegraf documentation: https://github.com/influxdata/telegraf/blob/release-1.31/plugins/outputs/loki/README.md

Created a PR with a fix

Added an example how to reproduce it

Currently I'm not sure, might be related to changes from T4519

IMO it would make sense to show the DUID since that has to be passed for static mappings and is also configured on the client side

Ok, that makes sense. Still need to place the tag.

The format I started playing with looks like this:

set system config-management commit-archive 1 username 'xxx'
set system config-management commit-archive 1 password 'xxx'
set system config-management commit-archive 1 scheme 'scp'
set system config-management commit-archive 1 location '192.0.2.1/backup'

I already looked a bit into it. What complicates it is the old location is a multi and one can add a list of locations.