-
Notifications
You must be signed in to change notification settings - Fork 230
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
Using umoci as a backend? #18
Comments
How do you compare it with BuildKit's (more accurately, containerd's) Either way, I think we can implement umoci-based implementation of containerd
Isn't it BuildKit LLB? https://github.com/moby/buildkit/blob/master/solver/pb/ops.proto <off-topic> |
I am fine with whatever works :) I mostly used buildkit because it had a lot of what I needed :) I didn't reimplement the LLB buildkit had already done that |
|
Well, There's also a question of adoption, but I'm not sure how many people use BuildKit at the moment. I know that several projects and companies have been using
Though of course, it should be noted, that not everyone uses containerd as a base for everything (LXC/LXD use
I don't know what LLB stands for, can someone give me a tl;dr? |
TLDR: LLB is to Dockerfile what LLVM IR is to C.
|
But does it still have the same drawbacks as Dockerfiles (in other words, is it just another representation or is it actually something new?). Is there a document online about it somewhere (I couldn't find it after a bit of Googling)? |
I consider LLB is new and anyone can implement new languages that might solve Dockerfile drawbacks. e.g. Build secret, INCLUDE, UNSETENV, ..., and whatever. Design doc: moby/moby#32925 Tonis's presentation https://www.slideshare.net/mobile/Docker/state-of-builder-and-buildkit |
Also, could you open github issue about README readability? https://github.com/moby/buildkit/issues Maybe we should have FAQ section? |
opened moby/buildkit#293 for clarifying LLB |
I was wondering if you were interested in using umoci as a backend, so that you don't have to use the "dodgy" FUSE backend or
overlayfs
(which requires either root or an Ubuntu kernel + user namespaces).umoci unpack --rootless
works on effectively everything I've tried it on. You can take a look at https://github.com/cyphar/orca-build (which is a rootless image builder I wrote quite a long time ago) to see how it works in practice.(Also, as an aside, now that we have
img
andorca-builder
and Akihiro'sPRoot
plans andBuildKit
and ..., maybe we should start consolidating some of these projects at some point? Re-implementing Dockerfiles isn't something that should be burning 5+ projects worth of development time IMHO.)The text was updated successfully, but these errors were encountered: