-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Generate cri-o container runtime preload tarball #8581
Conversation
Codecov Report
@@ Coverage Diff @@
## master #8581 +/- ##
==========================================
- Coverage 32.14% 32.05% -0.09%
==========================================
Files 161 161
Lines 10494 10523 +29
==========================================
Hits 3373 3373
- Misses 6717 6746 +29
Partials 404 404
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you plz test it manually ? You can generate preload tar and then put it in the cache folder and if it works successfully we will merge it and let the cron job create the tars
It seems to auto-upload, so I guess I need to comment that out... And need to determine if that “cache” folder is required by the “storage” So maybe need the preload part as well, to see whether it actually works ? |
fdbab9f
to
1bf268c
Compare
I included everything for now, until I actually know what is in those databases...
Note that the "sigstore" and "mounts" are empty, so it's just about "cache". Seems to have worked otherwise. Tested with just the default k8s version.
Note: that this Step 1 was only about creating the tarball, not about using it |
The name "overlay2" seems to be hard-coded. It was supposed to be "overlay"... // TarballName returns name of the tarball
func TarballName(k8sVersion, containerRuntime string) string {
return fmt.Sprintf("preloaded-images-k8s-%s-%s-%s-overlay2-%s.tar.lz4", PreloadVersion, k8sVersion, containerRuntime, runtime.GOARCH)
}
Fixed the name from the start. The actual API is a bit stupid (uses strings), so still hard-coded. if containerRuntime == "cri-o" {
storageDriver = "overlay"
} else {
storageDriver = "overlay2"
} |
New name:
|
@medyagh : trying to use preload with podman currently fails with the usual problem of overloading
So we should fix that one (#8056 #8100 #8179) first, before enabling this feature. But we need these tarballs, first. EDIT: This is only a problem for the KIC drivers, we can still use preloaded tarballs with the VM drivers |
Pretty much the same as containerd, minus Restart (cherry picked from commit d9fb2e0)
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: afbjorklund The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Tested locally, seems to work ok:
|
Travis tests have failedHey @afbjorklund, 1st Buildmake test
TravisBuddy Request Identifier: a9c15360-baf3-11ea-bd85-f15c2d376ac7 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank you
Added cri-o, to the list of preloaded tarballs:
For #6934