#Failing to build an image with Dockerfile and Go dagger sdk

1 messages · Page 1 of 1 (latest)

crude imp
#

Hello, I'm currently integrating go sdk on one of my experimentation. This little experiment build an image from a dockerfile but now i'm having this error :

failed to receive status: rpc error: code = Unavailable desc = error reading from server: command [docker exec -i dagger-buildkitd buildctl dial-stdio] has exited with exit status 137, please make sure the URL is valid, and Docker 18.09 or later is installed on the remote host: stderr=

This has something to do with this line somehow https://github.com/laupse/cloak-experimentation/blob/3c69cd275e4f1311e35ac76ce35c7ee16a881f13/magefiles/main.go#L59
And because of this i'm little bit confused with the difference between directory and filesystem ?

GitHub

Contribute to laupse/cloak-experimentation development by creating an account on GitHub.

thin locust
#

Hey @crude imp 👋

Regarding directory vs filesystem, the short answer is that filesystem has been replaced with directory. Before, most operations in cloak were on Filesystems, which had its limitations. Now we have Directory and Container instead, and the combination of the two unlock a lot of power!

As part of that change, I believe dockerfile() hasn't been implemented yet on the new schema. Let me find the issue for that

crude imp
#

Ok, thanks ! That's what i tough when i read the change of the core api (from far away)

thin locust