Closed seve closed 3 years ago
You can writing some word in a comment to trigger action:
/translate-title
It looks like there was a change somewhere in the newer versions of the Docker client that's distributed. I did https://github.com/docker-practice/actions-setup-docker/compare/master...nickvanw:master to work around it for now (manually installing a previous release), which seems to work for me.
Hope that's helpful!
now work!
We (https://github.com/dapr) are having this issue also, for example here: https://github.com/dapr/cli/actions/runs/936757774/workflow
@khs1994 can you please update this Github Action for everyone? Or perhaps @nickvanw could make a pull request that you can merge?
Can you please reopen this issue?
@nickvanw your changes do not resolve the problem for me. After open -g /Applications/Docker.app
the subsequent calls to docker
cannot find the command it seems. Same error message as before.
rerelease v1, now work
谢谢你帮我🙏
@khs1994 unfortunately I am still getting:
echo "-- Docker is ready."
+ sudo /bin/cp /Applications/Docker.app/Contents/Library/LaunchServices/com.docker.vmnetd /Library/PrivilegedHelperTools
+ sudo /bin/cp /Applications/Docker.app/Contents/Resources/com.docker.vmnetd.plist /Library/LaunchDaemons/
cp: /Applications/Docker.app/Contents/Resources/com.docker.vmnetd.plist: No such file or directory
+ sudo /bin/chmod 544 /Library/PrivilegedHelperTools/com.docker.vmnetd
+ sudo /bin/chmod 644 /Library/LaunchDaemons/com.docker.vmnetd.plist
chmod: /Library/LaunchDaemons/com.docker.vmnetd.plist: No such file or directory
+ sudo /bin/launchctl load /Library/LaunchDaemons/com.docker.vmnetd.plist
/Library/LaunchDaemons/com.docker.vmnetd.plist: No such file or directory
+ open -g /Applications/Docker.app
+ sleep 60
+ docker info
bash: line 12: docker: command not found
+ true
+ sleep 30
+ docker info
bash: line 16: docker: command not found
+ true
+ i=0
+ docker system info
+ (( i++ == 0 ))
+ printf %s '-- Waiting for Docker to finish starting up...'
+ sleep 1
-- Waiting for Docker to finish starting up...+ docker system info
+ (( i++ == 0 ))
+ printf .
+ sleep 1
.+ docker system info
+ (( i++ == 0 ))
+ printf .
+ sleep 1
.+ docker system info
+ (( i++ == 0 ))
+ printf .
+ sleep 1
.+ docker system info
+ (( i++ == 0 ))
+ printf .
+ sleep 1
.+ docker system info
+ (( i++ == 0 ))
+ printf .
.+ sleep 1
+ docker system info
+ (( i++ == 0 ))
etc
It never finishes
@khs1994 perhaps there was a caching issue where it still used an older release given the version number didn't change. Anyways, thanks a lot for the fast response! Much appreciated!
It seems that this just happens again. Seems like I'm not the only one: https://github.com/dapr/cli/runs/3515980595?check_suite_focus=true.
now pin docker for mac 3.6.x
It looks like a file isn't being found during docker installation leading to a installation failure. When the action goes to boot docker, it infinitely waits.
Significant Portion of Log:
Entire Log: