Upgrade to 1.0.3 breaks
jasonmcintosh opened this issue · 7 comments
[Error] This operation requires Docker version 17.07.0 or higher.
##[error]Process completed with exit code 1.
When I go back to 1.0.2 I'm able to run builds.
@jasonmcintosh
Version 1.0.3 includes only dependencies updates.
The default JFrog CLI version had been updated to 1.33.1. This verification had been introduced in JFrog CLI 1.33.0. You can still use 1.0.3 with JFrog CLI 1.32.4 by mention it in your workflow:
- uses: jfrog/setup-jfrog-cli@v1
with:
version: 1.32.4We're sorry for the inconvenience.
@jasonmcintosh,
I checked with my team about the docker version verification. This verification was put in place after we realized that docker login may not work properly when it is invoked by JFrog CLI, with version of docker below 17.07.
Hence, you are strongly recommended to use the default (or latest) JFrog CLI and upgrade the docker version. You can try Setup-Docker to upgrade docker to the latest version in Linux.
You may also need the latest JFrog CLI for your other issue.
Note the default github action is:
Docker version 3.0.10+azure, build 99c5edceb48d64c1aa5d09b8c9c499d431d98bb9
I've reverted back to 1.32.4 for now as it seems fine with the azure version.
Thanks for this information, @jasonmcintosh!
We are working on a fix: Instead of checking the docker client version, we will check the docker client API version.
You can track this PR: jfrog/jfrog-cli#623.
@jasonmcintosh,
JFrog CLI 1.35.1 is released. This version includes the fix.
Feel free to upgrade.
We'll appreciate your feedback for that!
Clarification - JFrog CLI 1.35.1 includes the fix, but it is not the default version of the setup-jfrog-cli GitHub Action. The CLI version needs to be set, as described in the Action's documentation.
@jasonmcintosh,
Version 1.0.4 of the setuo-jfrog-cli GitHub Action is released and includes the latest JFrog CLI release as the default. Please let us know if it resolves the issue for you.