-
Notifications
You must be signed in to change notification settings - Fork 406
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
Share kodata across multi-arch builds? #262
Comments
This issue is stale because it has been open for 90 days with no |
This might be a little more complicated now with Windows support, since kodata is laid out differently in Windows layers. I wonder if we could just not include the layer if kodata isn't present, rather than include an empty layer. |
I think we want the directory to exist, even if it is empty. |
Sure. What if we put the empty /var/run/kodata in the same layer as the binary, and if there's anything in kodata, put the rest in the separate layer. That way if there isn't any kodata we can skip a layer. (This is also complicated by Windows-vs-Linux containers, but maybe a bit less) |
I don't have a problem with that, though you should confirm it WAI since I think the layers are in the wrong order. |
Kindly ping here; maybe we cannot add the data layer that includes /cc @Dentrax Lines 822 to 842 in 5e0452a
|
I think we want to make sure there's an empty The reason is that some code may depend on the var existing today even if it's empty, and changing that would break them. The change is that |
Talking to @jonjohnsonjr I realized that we might be able to save some cycles if we found a way to share the kodata layer across architectures in multi-arch builds. Right now we are deterministically producing the same layer N times, but it should be safe to share this if we can find a way to reasonably do so.
The text was updated successfully, but these errors were encountered: