Buildkitd failed gRPC error: Unavailable : all SubConns are in TransientFailure
Hi. Trying to play with Shipa in EKS and followed all the installation instructions, however, `shipa-init-job` pesistently fails with the following errors message: ``` waiting busybody daemons... Error: Buildkitd failed gRPC error: Unavailable : all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: Error while dialing dial tcp :0: connect: connection refused" ``` I've identified that `shipa add-platform static` (and any other platform for that matter) throws buildkit errors. Is there any workaround / fix for it? Also, what's the relationship between Shipa and Ketch?
Posted by Martin almost 2 years ago
Hello Shipa is Free and OpennSource ?
Posted by Kiven WANDA over 2 years ago
Can Shipa work with OpenShift 3.x and 4.x on-prem clusters?
Posted by anon over 2 years ago
Hello, Just wondering where on your roadmap might serverless support be? As we use GCP Cloud Run and Functions as well as Kubernetes. I think the product could help us.
Posted by Matthew about 1 year ago
Posted by mansha almost 2 years ago