-
Notifications
You must be signed in to change notification settings - Fork 351
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
Run tests used in various high-level container runtimes #331
Comments
Sure, I would like to work on it. |
@nasirhm Sure! I assigned you. This issue is very abstract. If you have any questions, please let me. |
Thank You @utam0k , Are we planning to set up CI Pipelines to test Youki with Docker, Podman, Containerd and CRI-O ? |
Yes, however, if you have a better way, that is fine. |
@nasirhm Hello. Do you have any problems? I can help you ;) |
Sorry for replying in this instead of opening a new one.(I think my question is very similar to this one. ) I am trying to find a way to tell containerd to use the youki instead of runc. But I don’t know how to do. Is there some relevant documents? |
@Yuan-Zhuo
|
Thanks for your reply! I also tried to modify the runtime in /etc/containerd/config.toml before, but it didn't work.
It can be seen from the error message that the replacement is successful, because the error report of runc will be
But it seems that we cannot get the real runtime from the go program( I am not sure about the mechanism of this package) package main
import (
"fmt"
"log"
"github.com/containerd/containerd"
)
func main() {
if err := testCrun(); err != nil {
log.Fatal(err)
}
}
func testCrun() error {
client, err := containerd.New("/run/containerd/containerd.sock")
if err != nil {
return err
}
defer client.Close()
# get runtime
fmt.Println(client.Runtime())
return nil
} No matter it is runc, crun or youki, the output is always like this
|
for the specifics of testing I think the best fit would be tekton-cd as it supports using the runtimeClassName annotation for cloud-native ci/cd tasks. example: apiVersion: tekton.dev/v1alpha1
kind: TaskRun
metadata:
name: pipeline-test-auth
namespace: default
spec:
params:
- name: revision
value: v1alpha1
serviceAccountName: build-bot
podTemplate:
securityContext:
runAsNonRoot: true
runAsUser: 1724
runtimeClassName: kata |
@gattytto |
Overview
The actual use of youki is high-level container runtime. So the ci should be included to make sure that it can be used with some of the major high-level container runtimes.
Target
The text was updated successfully, but these errors were encountered: