Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[Bug]: dockerd hits 100% CPU usage when viewing container logs #7693

@scherddel

Description

@scherddel

Error Message and Logs

PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
872 root      20   0 3877128 122732  63744 S 103.0   1.5  27:27.95 dockerd

Steps to Reproduce

When attempting to view logs for a git-based Docker application, the dockerd process on the underlying host spikes to 100% CPU usage. The logs fail to load in the UI, displaying only the "Refresh to see logs" message. The issue persists until the Docker service itself is restarted on the host.

Note: This issue is intermittent and seems tied to session longevity.

1 .Keep a Coolify dashboard session open for an extended period or through a Coolify instance update.

  1. Navigate to a Project > Environment > Application.

  2. Click on the Logs tab.

  3. The UI fails to stream logs ("Refresh to see logs").

  4. Observe host resources; dockerd begins consuming 100% of a CPU core.

Example Repository URL

No response

Coolify Version

latest

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

No response

Additional Information

Is there anything I can do to help to debug this issue? any specific log etc that should be checked?

Metadata

Metadata

Assignees

No one assigned

    Labels

    🔍 TriageIssues that need assessment and prioritization.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions