Skip to content

Only connect to buildkitd backend lazily #633

Description

@kmannislands

What existing functionality needs improvement?

Some commands that don't actually end up needing buildkit still eagerly connect to it which can be slow if local buildkitd in docker isn't already running or in various remote buildkitd scenarios

Expected Behavior

Only connect to buildkit when needed. Make connection lazy in the codebase

Bonus points: commands that are pure LOCALLY could run without ever needing buildkitd. We should connect (or start) only when actually needed by a non-LOCALLY FROM command (note: this may conflict with semantics of implicit +base)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Fields

    No fields configured for Feature.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions