Open saphoooo opened 5 years ago
Nobody experienced the same issue? Any idea to help me investigate further?
Hi @saphoooo I tried to build the image using gvisor in minikube and I was able to build successfully. I'm not very familiar with gvisor in general though; you could try opening an issue in the gvisor repo to see if they are familiar with this bug?
Ok, I've opened an issue #122. Did you use cri-o for building your image in minikube or cri-o as I did?
minikube requires containerd as the container runtime to enable gvisor
Unfortunately cri-o is not a supported container runtime for this project, closing out as won't fix for now. We can certainly have a larger discussion around cri-o in the future if there's sufficient community demand.
okay I apparently lied -- crio has been added, will recheck the steps to reproduce...
Priya, if you could do a quick eyeball with the latest minikube that would be glorious
okay, gviso + crio still an issue -- moving this to blocked
Actual behavior I'm trying to build an image in Kubernetes with runsc, but it fails with error message:
Expected behavior Without sandboxing in gVisor, the same build works well and push the image to the registry.
To Reproduce Steps to reproduce the behavior:
Additional Information
Error Message