MCPcopy
hub / github.com/google/cadvisor / CrioActions

Interface CrioActions

integration/framework/framework.go:151–161  ·  view source on GitHub ↗

CrioActions provides methods for managing CRI-O containers in tests. CRI-O containers run inside pod sandboxes, so each container requires a pod to be created first.

Source from the content-addressed store, hash-verified

149// CRI-O containers run inside pod sandboxes, so each container requires
150// a pod to be created first.
151type CrioActions interface {
152 // Run the no-op pause CRI-O container and return its ID.
153 RunPause() string
154
155 // Run the specified command in a CRI-O busybox container and return its ID.
156 RunBusybox(cmd ...string) string
157
158 // Runs a CRI-O container in the background. Uses the specified CrioRunArgs and command.
159 // Returns the ID of the new container.
160 Run(args CrioRunArgs, cmd ...string) string
161}
162
163// CrioRunArgs contains arguments for running a CRI-O container.
164type CrioRunArgs struct {

Implementers 3

dockerActionsintegration/framework/framework.go
crioActionsintegration/framework/framework.go
containerdActionsintegration/framework/framework.go

Calls

no outgoing calls

Tested by

no test coverage detected

Used in the wild real call sites across dependent graphs

searching dependent graphs…