-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Proposal: mixed-platform (mixed-worker?) LLB #41
Comments
I wonder if this can be solved same way as distributed workers. How different is it to build with two workers that use different execution/snapshots vs two workers that are on different nodes. The other side of it is making sure that some vertexes can be only executed on a specific set of workers. My first thought is to not include that info into the vertex data(the part that affects the digests) but add a way to send additional metadata with them. As Dockerfile frontend needs to pull the image configuration anyway to get the base image env/workdir it should be able to determine the platform restriction of these vertexes. |
Yes, I'm unsure future LCOW will use two containerd instances or single I think we can close this issue for housekeeping purpose atm. |
link: containerd-side LCOW proposal containerd/containerd#1185 |
let me reopen this issue for tracking purpose |
Seems closable now |
Co-authored-by: Vlad A. Ionescu <[email protected]>
feat: report status to depot API
For LCOW
moby/moby#33854
moby/moby#33850
The text was updated successfully, but these errors were encountered: