Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Buildkit doesn't work on DigitalOcean Kube cluster #55

Open
kklin opened this issue Dec 21, 2020 · 0 comments
Open

Buildkit doesn't work on DigitalOcean Kube cluster #55

kklin opened this issue Dec 21, 2020 · 0 comments

Comments

@kklin
Copy link
Member

kklin commented Dec 21, 2020

What happened?

❯ blimp up
Booting cloud sandbox
[Error] Get help at https://kelda.io/blimp/docs/help/
Message: Failed to create development sandbox
Error: rpc error: code = Unavailable desc = transport is closing

The buildkit pod is unhealthy, with the following logs:

time="2020-12-21T04:38:58Z" level=warning msg="/proc/sys/kernel/unprivileged_userns_clone needs to be set to 1."
[rootlesskit:parent] error: failed to start the child: fork/exec /proc/self/exe: operation not permitted

What were you expecting to happen?

Buildkit should successfully start, and the development sandbox should be deployed.

There's some additional UX issues here as well:

  • The error message should be better.
  • The compose file doesn't even require building images. So even if buildkit isn't working, we should let the development sandbox be created.

Reproduction steps

Additional context

Switching to non-rootless images for buildkit may fix the issue on DO.

Reported by Ian Walter in Slack (https://kelda.slack.com/archives/C4LF0KL4D/p1608525499118200)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant