Documentation ¶
Overview ¶
Package containerizer provides the implementations to store data about [Container] and [ContainerEngine] objects. Subpackages provide so-called “containerizers” (implementing Containerizer) that discover Containers from specific container engines.
Nota bene: the lxkns model defines only the model.Container and model.ContainerEngine interfaces instead of implementations in order to break import cycles that otherwise would invariably occur.
Nota bene-bene: sometimes, preemptive interfaces are simply necessary, because they don't have any idea of Golotry. especially, when the domain-specific (namespace) language uses type inheritance and embedding doesn't eat the cake.
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
This section is empty.
Types ¶
type Containerizer ¶
type Containerizer interface { // Discover user-level "alive" containers. // // Please note that depending on the particular containerizer implementation // the context might be used or not used at all. Containers(ctx context.Context, procs model.ProcessTable, pidmap model.PIDMapper) []*model.Container // Close and release all resources allocated by this Containerizer. Close() }
Containerizer discovers containers and relates them to processes (and thus also to Linux-kernel namespaces). A Containerizer can optionally be passed to a namespace discovery via the discovery options; the containerizer then will be called in order to discover any "alive" containers.
Directories ¶
Path | Synopsis |
---|---|
Package whalefriend implements a [containerizer.Containerizer] that discovers containers from container engines supported by the [@thediveo/whalewatcher] module, such as Docker and containerd (moby & friends).
|
Package whalefriend implements a [containerizer.Containerizer] that discovers containers from container engines supported by the [@thediveo/whalewatcher] module, such as Docker and containerd (moby & friends). |