Geeting errors when using podman socket to get logs with docker_logs source in vector

[harikeshtripathi]

My product supports "docker" and "podman" both as container runtime. We are trying to replace our home grown log handler with Vector. Support for both docker and podman are critical to us.

We have tried capturing log using "docker_logs" source from docker.sock and podman.sock. But while using podman it looks like Vector is not working properly. I see below errors in vector logs when using it with podman.

2025-02-06T06:58:08.641980Z ERROR source{component_kind="source" component_id=my_source_id component_type=docker_logs}: vector::internal_events::docker_logs: Error in communication with Docker daemon. error=RequestTimeoutError error_type="connection_failed" stage="receiving" container_id=None internal_log_rate_limit=true

I would like to know when this error is thrown - "Error in communication with Docker daemon". What are the after effects of this ? Will the "docker_logs" source not get any logs after this error is hit ?

Also on podman we have seen that as soons as all the containers stop Vector container also exits. Is there config setting we can use to prevent this ?

[pront]

I would like to know when this error is thrown - "Error in communication with Docker daemon". What are the after effects of this ?

Socket permission issues can prevent Vector from communicating with the Podman daemon.

Also, what's your podman version? See #6807.

Will the "docker_logs" source not get any logs after this error is hit ?

Correct, unless you fix the error and reload or restart.

Also on podman we have seen that as soons as all the containers stop Vector container also exits. Is there config setting we can use to prevent this ?

This sounds like a bug. Do you see any logs before it exits?