What steps did you take and what happened
I was trying to use this against a colima-based environment, which is essentially a VM running k3s for macOS. My setup is using contained versus docker.
When I run kubectl build . I see errors like this:
=> => # Warning buildkit-5ccb4cf857-n5fsx Failed Error: failed to generate container "f61e0f583462c6533a262e462577aff3bf4accff4b3
=> => # 71cf9d54364a2042a14e4" spec: failed to generate spec: path "/tmp" is mounted on "/tmp" but it is not a shared mount
and then it basically hangs indefinitely.
I was able to fix this by connecting to the VM with colima ssh and running this:
sudo mount --make-shared / # for /var/log
sudo mount --make-shared /tmp
sudo mount --make-shared /run
sudo mount --make-shared /var/lib
exit
It seems that settings that are required on the node should be well documented, and as mentioned in https://github.com/vmware-tanzu/buildkit-cli-for-kubectl/issues/107 it would be great if some things could be configured, like what directories to mount, and where the sockets, etc are located on the nodes.
What did you expect to happen
I expected kubectl build . to work with a basic test.
Environment Details:
I ended up building the plugin while I was doing my testing.
kubectl buildkit version (use kubectl buildkit version)
Client: v0.1.5-8-g5db0221
Builder: no builder pods are running
Kubernetes version (use kubectl version)
Client Version: v1.24.0
Kustomize Version: v4.5.4
Server Version: v1.22.4+k3s1
Where are you running kubernetes (e.g., bare metal, vSphere Tanzu, Cloud Provider xKS, etc.)
k3s
Container Runtime and version (e.g. containerd sudo ctr version or dockerd docker version on one of your kubernetes worker nodes)
What steps did you take and what happened I was trying to use this against a
colima-based environment, which is essentially a VM running k3s for macOS. My setup is using contained versus docker.When I run
kubectl build .I see errors like this:I was able to fix this by connecting to the VM with
colima sshand running this:And then on my local system I ran:
and things worked fine.
It seems that settings that are required on the node should be well documented, and as mentioned in https://github.com/vmware-tanzu/buildkit-cli-for-kubectl/issues/107 it would be great if some things could be configured, like what directories to mount, and where the sockets, etc are located on the nodes.
What did you expect to happen
I expected
kubectl build .to work with a basic test.Environment Details:
I ended up building the plugin while I was doing my testing.
kubectl buildkit version)kubectl version)k3ssudo ctr versionor dockerddocker versionon one of your kubernetes worker nodes)Builder Logs [If applicable, an excerpt from
kubectl logs -l app=buildkitfrom around the time you hit the failure may be very helpful]Error from server (BadRequest): container "buildkitd" in pod "buildkit-5ccb4cf857-n5fsx" is waiting to start: CreateContainerErrorVote on this request
This is an invitation to the community to vote on issues. Use the "smiley face" up to the right of this comment to vote.