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

Proposal: mixed-platform (mixed-worker?) LLB #41

Closed
AkihiroSuda opened this issue Jun 29, 2017 · 5 comments
Closed

Proposal: mixed-platform (mixed-worker?) LLB #41

AkihiroSuda opened this issue Jun 29, 2017 · 5 comments
Labels

Comments

@AkihiroSuda
Copy link
Member

For LCOW
moby/moby#33854
moby/moby#33850

@tonistiigi
Copy link
Member

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.

@AkihiroSuda
Copy link
Member Author

Yes, I'm unsure future LCOW will use two containerd instances or single containerd.exe instance with two runtimes, but even if latter, we could just define two workers for single containerd.exe instance.

I think we can close this issue for housekeeping purpose atm.

@AkihiroSuda
Copy link
Member Author

link: containerd-side LCOW proposal containerd/containerd#1185

@AkihiroSuda
Copy link
Member Author

let me reopen this issue for tracking purpose

@AkihiroSuda
Copy link
Member Author

Seems closable now

alexcb pushed a commit to alexcb/buildkit that referenced this issue Jun 2, 2021
goller added a commit to goller/buildkit that referenced this issue Sep 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants