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
After upgrading to version 1.3.0, sbt started throwing "docker: 'version --format '{{.Server.Version}}'' not a docker command" warnings on console
#1051
Closed
kpritam opened this issue
Oct 24, 2017
· 2 comments
Upgrading to packager version 1.3.0 should not result into any warnings on console
E.g. Just run sbt
Actual behaviour
After upgrading to sbt-native-packager 1.3.0, can see following warnings on sbt console:
docker: 'version --format '{{.Server.Version}}'' is not a docker command.
I have docker v17.09.0-ce-mac35 (19611) installed on my machine and it does give me correct version when above command is run from separate terminal: ~/T/csw-prod:master$ docker version --format '{{.Server.Version}}' 17.09.0-ce
Information
What sbt-native-packager are you using?
1.3.0
What sbt version
1.0.2
What is your build system (e.g. Ubuntu, MacOS, Windows, Debian )
macOs (iterm2 3.1.3)
The text was updated successfully, but these errors were encountered:
Thanks for your detailed bug request and trying out the new release.
I hope this is not an issue with the way java spawns external processes. I'm not familiar with docker on mac, but there is still a vm involved to run docker, right?
Expected behaviour
Upgrading to packager version 1.3.0 should not result into any warnings on console
E.g. Just run
sbt
Actual behaviour
After upgrading to sbt-native-packager 1.3.0, can see following warnings on sbt console:
docker: 'version --format '{{.Server.Version}}'' is not a docker command.
I have docker v17.09.0-ce-mac35 (19611) installed on my machine and it does give me correct version when above command is run from separate terminal:
~/T/csw-prod:master$ docker version --format '{{.Server.Version}}'
17.09.0-ce
Information
What sbt-native-packager are you using?
1.3.0
What sbt version
1.0.2
What is your build system (e.g. Ubuntu, MacOS, Windows, Debian )
macOs (iterm2 3.1.3)
The text was updated successfully, but these errors were encountered: