Closed carbocation closed 10 months ago
Hi @carbocation! Thanks for reporting.
I don't believe there's a way to bypass this specifically at the moment. Fortunately, gcloud docker
is explicitly called in one place in the local provider's runner script here. This can be changed to instead use docker (and perhaps set up the credential helpers).
I do see that using gcloud docker
has been deprecated for a while now, so I expect this to be fixed in the next release.
I don't have a great test case for this right now, but I do believe that the last gcloud docker
call indeed has been removed, so this can probably be closed.
Thanks!
Fixed by #261 (Release 0.4.9)
When I run the "Hello World" test for the
local
provider, it works. When I run it on a custom image, it also works. But when I try to make it run on on anygcr.io/
image, it does not work. Instead, I get the following message in therunner-log.txt
file:Given the contents of the error message, and the fact that I have docker version 20 installed, I think this error is not surprising. But is there a way to bypass dsub calling
gcloud docker
when runninggcr.io
images with the--local
provider so that those of us with docker > 18.03 can use the--local
provider?