You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Docker CLI already exists in the repo but inside the docker package in the root repo. The CLI does not need a Docker daemon running on the same host, and does not requires any privileges if the connected daemon allows the client.
My request is to split the CLI from the docker package and put it as docker-cli in the main repo with docker (or smth like docker-daemon) marked as recommands. The same would apply to docker-compose which is just a plugin of the CLI.
Why is it worth to add this package?
The Docker CLI already exists in the repo but inside the
dockerpackage in the root repo. The CLI does not need a Docker daemon running on the same host, and does not requires any privileges if the connected daemon allows the client.My request is to split the CLI from the
dockerpackage and put it asdocker-cliin the main repo withdocker(or smth likedocker-daemon) marked as recommands. The same would apply todocker-composewhich is just a plugin of the CLI.Home page URL
https://docker.com
Source code URL
https://github.com/docker/cli.git
Packaging policy acknowledgement
The project is actively developed.
The project has existing packages and is "well known".
Licensed under an open source license.
Not available through a language package manager: cargo, cpan, dotnet tool, gem, npm, pip, etc.
Not taking up too much disk space (< 100MiB per architecture, exceptions can be made)
Not duplicating the functionality of existing packages.
Not serving hacking, malware, phishing, spamming, spying, ddos functionality.
I certify that I have read Termux Packaging Policy and understand that my request will be denied if it is found lacking.
Additional information
No response