Open datafoo opened 1 year ago
@datafoo I assume you are using the docker executor.
I would assume this warning is also produced when you start a container from the docker cli.
Could you verify this.
I forgot to indicate that the issue is not appearing all the time I run my CI pipelines. It comes randomly.
I tried starting the a container from the cli but everything seems fine. The logs starting from "Jul 12 07:15:30" are for the manually started container.
[root@mymachine.example.com:~]# docker run alpine
[root@mymachine.example.com:~]# journalctl -u systemd-networkd.service -f
Jul 12 07:10:44 mymachine systemd-networkd[1739]: veth36bbb91: Link DOWN
Jul 12 07:10:44 mymachine systemd-networkd[1739]: veth20f9be7: Lost carrier
Jul 12 07:10:44 mymachine systemd-networkd[1739]: veth20f9be7: Link DOWN
Jul 12 07:10:45 mymachine systemd-networkd[1739]: docker0: Lost carrier
Jul 12 07:15:30 mymachine systemd-networkd[1739]: veth26607e9: Link UP
Jul 12 07:15:31 mymachine systemd-networkd[1739]: veth26607e9: Gained carrier
Jul 12 07:15:31 mymachine systemd-networkd[1739]: docker0: Gained carrier
Jul 12 07:15:31 mymachine systemd-networkd[1739]: veth26607e9: Lost carrier
Jul 12 07:15:31 mymachine systemd-networkd[1739]: veth26607e9: Link DOWN
Jul 12 07:15:31 mymachine systemd-networkd[1739]: docker0: Lost carrier
Describe the bug
When using
services.gitlab-runner
and a job is processed, many warnings of the style "veth***: Failed to manage SR-IOV PF and VF ports, ignoring: Invalid argument" are logged.Steps To Reproduce
Steps to reproduce the behavior:
services.gitlab-runner
andsystemd-networkd
.Expected behavior
No warning logs should appear.
Additional context
A similar issue was logged in https://github.com/systemd/systemd/issues/27369 and in https://github.com/moby/moby/issues/45480.
More logs:
Notify maintainers
@bachp
Metadata
Please run
nix-shell -p nix-info --run "nix-info -m"
and paste the result.