Skip to content

Conversation

@skartikey
Copy link
Contributor

Summary

  • Fixes regression where Telegraf fails to start when Docker/Podman daemon is unavailable
  • Start() now logs a warning instead of returning a fatal error when connection fails
  • Client initialization is retried lazily on each Gather() cycle until successful
  • Restores pre-1.36.3 behavior where Telegraf starts regardless of Docker availability

Checklist

Related issues

resolves #18089

@telegraf-tiger telegraf-tiger bot added area/docker fix pr to fix corresponding bug plugin/input 1. Request for new input plugins 2. Issues/PRs that are related to input plugins labels Jan 5, 2026
@skartikey skartikey self-assigned this Jan 5, 2026
@skartikey skartikey changed the title fix(inputs.docker): Allow Telegraf to start when Docker daemon is una… fix(inputs.docker): Allow Telegraf to start when Docker daemon is unavailable Jan 5, 2026
…vailable

This fixes a regression introduced in v1.36.3 where Telegraf would fail to start if the Docker/Podman socket was unavailable. The Start() method now logs a warning instead of returning a fatal error, and the client connection is retried lazily on each Gather() cycle.
@skartikey skartikey force-pushed the inputs_docker_socket_missing branch from 7c2a47a to ec111c6 Compare January 5, 2026 19:17
@telegraf-tiger
Copy link
Contributor

telegraf-tiger bot commented Jan 5, 2026

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/docker fix pr to fix corresponding bug plugin/input 1. Request for new input plugins 2. Issues/PRs that are related to input plugins

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Telegraf 1.36.3-1 fails to start when Docker/podman socket is missing (regression from 1.36.2-1)

1 participant