Open tobiasoort opened 2 years ago
Looking at the logs for the buildkit container in the pod (which is the only one that actually failed):
$ kubectl logs -n kube-image -p builder-4rcj8 -c buildkit
buildkitd: could not lock /var/lib/buildkit/buildkitd.lock, another instance running?
That's weird right - why wouldn't it be able to get a lock?
While kim was originally developed to support rancher-desktop and generic uses I believe that RD has stopped shipping kim and does start up their own buildkit instance (looks like they still ship it but remove the kim builder). Even though kim runs buildkit in a container it does bind-mount a number of things from the host, including /var/lib/buildkit
. This might explain the conflict.
Worth asking about over at https://github.com/rancher-sandbox/rancher-desktop (I no longer work at SUSE/Rancher)
I'm running:
arkade get kim
on Ubuntukim builder install
on UbuntuResult:
On the kubectl side:
So lets
describe
the offending pod:I have no clue why this pod is crashlooping. I've not been able to get
kim
to work on this machine. I'd love to use it so I can not deal with shuffling images by hand.