stefanscherer/docker-cli-builder

Build Docker CLI for Windows

docker-cli-builder

Build Docker CLI for Windows from upstream repo https://github.com/docker/cli and publish the docker.exe to GitHub releases https://github.com/StefanScherer/docker-cli-builder/releases.

docker-cli-builder's Issues

Request: Update build from new cli

Hi @StefanScherer!

Since 19.03.1 cli was recently posted is there any chance since you've got this set job already set up so nicely in Appveyor you could possibly kick it off to build 19.03.1?

Thanks!

Binaries available from Docker

Docker is apparently distributing docker and dockerd binaries on the downlow without advertising their existence. Currently up to version 20.10.14: https://download.docker.com/win/static/stable/x86_64/

Keep Chocolatey package updated

Current version of this project published to Chocolatey is 19.03.12. Current version according to this repository is 20.10.9.

There are some posts on the Choco package itself asking for updates as well.

I'm unsure what you have set up in AppVeyor beyond the build script in this repository. If there is no automated push to the Chocolatey repo, it would be quite easy to set up a GitHub action which triggers on release. If you want, I can help you set this up.

Add Windows ARM64 build

I have no idea if it would build out of the box, but if you have the right Visual Studio tools to target ARM64, then it should be possible to give it a shot.

My goal would be to see how difficult it would be to use the Docker CLI on a Surface Pro X, with the Docker Engine running elsewhere.

The real Docker host could be Windows Server 2019 or Linux, but I am also curious to give it a shot with the recent ACI integration.

This being said, I could try using an x86 build of the Docker CLI with the emulation available on ARM64.

Docker build using Docker Cli on windows

I am using this cli tool on windows to connect to docker daemon hosted on a linux system. I am facing issue while running "docker build" against my Dockerfile created for a dotnet core project. And it fails at the step where it will restore the nuget packages. Not sure what is the reason.
Below is the error.
/usr/share/dotnet/sdk/2.1.807/NuGet.targets(123,5): error : Unable to load the service index for source https://api.nuget.org/v3/index.json.

/usr/share/dotnet/sdk/2.1.807/NuGet.targets(123,5): error : No such device or address

But the same works perfectly fine when I login to the Dockerhost and try to run it from there .

Could you please help me here ? Will docker cli tool for windows does not support all the commands or any special configuration to be done ? Note that I am using ssh connection to connect from docker-cli to docker host.

Build Failing

Looks like the automated build has been failing for awhile now. Are there plans to get it working again?

Secrets exposed in GHA workflows

I'm not sure the ramifications but the secrets should be removed and release artifacts should likely be audited.

https://github.com/StefanScherer/docker-cli-builder/blob/master/appveyor.yml#L34

Upload as nuget package

Are there any plans to create a NuGet package out of the Docker-CLI executable? That way it would be easier to use in for example Cake Build.

20.10.21 does not have binary available

It looks like the release for 20.10.21 does not have a binary avaialble, just the source files.

AppVeyor fails due to a problem with the windowsservercore image

`Build started
git clone -q https://github.com/StefanScherer/docker-cli-builder.git C:\projects\docker-cli-builder
git fetch -q origin +refs/pull/9/merge:
git checkout -qf FETCH_HEAD
docker build -t docker-cli-builder .
Sending build context to Docker daemon 113.2kB
Step 1/16 : FROM microsoft/windowsservercore
docker : manifest for microsoft/windowsservercore:latest not found
At line:1 char:1

• docker build -t docker-cli-builder .

•   + CategoryInfo          : NotSpecified: (manifest for mi...atest not found:String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError
  
  

Command executed with exception: manifest for microsoft/windowsservercore:latest not found`