Skip to content

Define a plan for HTTP engine API #32873

@vieux

Description

@vieux

The docker CLI is moving to it's own repository, docker/cli See #32694

The current plan is to leave the HTTP engine API in the moby repo. It will work for now because "docker engine" is still a monolith, but it will get problematic as soon as we start splitting it into components.

We need a plan moving forward. Suggestions welcome :D

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/apiAPIarea/projectpriority/P1Important: P1 issues are a top priority and a must-have for the next release.roadmap

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions