Open Shaked opened 3 years ago
This feels like it might be a duplicate of #79 perhaps. Try using fully qualified registry names on both your build tag and run tag and see if that solves this.
If not, can you see what kubectl describe pod XXX
looks like on these failing pods, and perhaps copy the tail-end of the build output - perhaps there's something there that will help shed light on what's going wrong.
Another thing to check is the image pull policy on the pods to make sure it's not getting set to always pull.
@Shaked The problem could be is that the Image might be getting built on one node and the pod is being deployed on another node which doesn't contain the Image. I am also currently facing in same Issue in Amazon EKS. Some times it work but most of the time it it failing.
What steps did you take and what happened
I have ran the following commands:
Sometimes it might work but most of the times it ends with:
What did you expect to happen
I expect the newly built image to be in AKS and run.
Environment Details:
kubectl buildkit version
):v0.1.3
kubectl version
):sudo ctr version
or dockerddocker version
on one of your kubernetes worker nodes):Server: Version: 1.4.4+azure Revision: 05f951a3781f4f2c1911b05e61c160e9c30eaa8e UUID: 5c6ac07c-7cd8-4b02-84e9-402d66fec664
docker version Client: Version: 19.03.14+azure API version: 1.40 Go version: go1.13.15 Git commit: fd3371eb7df1adeceff5935cf3ade0576a0f48d5 Built: Sat Oct 24 07:44:17 2020 OS/Arch: linux/amd64 Experimental: false
Server: Engine: Version: 19.03.14+azure API version: 1.40 (minimum version 1.12) Go version: go1.13.15 Git commit: 7d75c1d40d88ddef08653dbd611f41df42bdf087 Built: Mon Mar 12 00:00:00 2018 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.4.4+azure GitCommit: 05f951a3781f4f2c1911b05e61c160e9c30eaa8e runc: Version: 1.0.0-rc92 GitCommit: ff819c7e9184c13b7c2607fe6c30ae19403a7aff docker-init: Version: 0.18.0 GitCommit: