Directories ¶
Path | Synopsis |
---|---|
Package annotations defines OCI annotations
|
Package annotations defines OCI annotations |
api
|
|
Package apparmorutil provides utilities for AppArmor
|
Package apparmorutil provides utilities for AppArmor |
cmd
|
|
Package containerdutil provides "caching" versions of containerd native snapshotter and content store.
|
Package containerdutil provides "caching" versions of containerd native snapshotter and content store. |
hostsstore
Package hostsstore provides the interface for /var/lib/nerdctl/<ADDRHASH>/etchosts .
|
Package hostsstore provides the interface for /var/lib/nerdctl/<ADDRHASH>/etchosts . |
Package identifiers implements functions for docker compatible identifier validation.
|
Package identifiers implements functions for docker compatible identifier validation. |
idutil
|
|
pull
Package pull forked from https://github.com/containerd/containerd/blob/v1.4.3/cmd/ctr/commands/content/fetch.go
|
Package pull forked from https://github.com/containerd/containerd/blob/v1.4.3/cmd/ctr/commands/content/fetch.go |
push
Package push derived from https://github.com/containerd/containerd/blob/v1.4.3/cmd/ctr/commands/images/push.go
|
Package push derived from https://github.com/containerd/containerd/blob/v1.4.3/cmd/ctr/commands/images/push.go |
inspecttypes
|
|
dockercompat
Package dockercompat mimics `docker inspect` objects.
|
Package dockercompat mimics `docker inspect` objects. |
Package labels defines labels that are set to containerd containers as labels.
|
Package labels defines labels that are set to containerd containers as labels. |
k8slabels
Package k8slabels defines Kubernetes container labels
|
Package k8slabels defines Kubernetes container labels |
Forked from https://github.com/kubernetes/kubernetes/blob/cc60b26dee4768e3c5aa0515bbf4ba1824ad38dc/staging/src/k8s.io/cri-client/pkg/logs/logs_other.go Copyright The Kubernetes Authors.
|
Forked from https://github.com/kubernetes/kubernetes/blob/cc60b26dee4768e3c5aa0515bbf4ba1824ad38dc/staging/src/k8s.io/cri-client/pkg/logs/logs_other.go Copyright The Kubernetes Authors. |
Package nsutil provides utilities for namespaces.
|
Package nsutil provides utilities for namespaces. |
Package resolvconf provides utility code to query and update DNS configuration in /etc/resolv.conf originally from https://github.com/moby/moby/blob/6014c1e29dc34dffa77fb5749cc3281c1b4854ac/libnetwork/resolvconf/resolvconf.go
|
Package resolvconf provides utility code to query and update DNS configuration in /etc/resolv.conf originally from https://github.com/moby/moby/blob/6014c1e29dc34dffa77fb5749cc3281c1b4854ac/libnetwork/resolvconf/resolvconf.go |
Package sysinfo is a copy of https://github.com/moby/moby/tree/master/pkg/sysinfo as of cff4f20c44a3a7c882ed73934dec6a77246c6323 This may be removed (and replaced by a dependency to moby again) once they have migrated to containerd v2.
|
Package sysinfo is a copy of https://github.com/moby/moby/tree/master/pkg/sysinfo as of cff4f20c44a3a7c882ed73934dec6a77246c6323 This may be removed (and replaced by a dependency to moby again) once they have migrated to containerd v2. |
portlock
portlock provides a mechanism for containers to acquire and release ports they plan to expose, and a wait mechanism This allows tests dependent on running containers to always parallelize without having to worry about port collision with any other test Note that this does NOT protect against trying to use a port that is already used by an unrelated third-party service or container Also note that *generally* finding a free port is not easy: - to just "listen" and see if it works won't work for containerized services that are DNAT-ed (plus, that would be racy) - inspecting iptables instead (or in addition to) may work for containers, but this depends on how networking has been set (and yes, it is also racy) Our approach here is optimistic: tests are responsible for calling Acquire and Release
|
portlock provides a mechanism for containers to acquire and release ports they plan to expose, and a wait mechanism This allows tests dependent on running containers to always parallelize without having to worry about port collision with any other test Note that this does NOT protect against trying to use a port that is already used by an unrelated third-party service or container Also note that *generally* finding a free port is not easy: - to just "listen" and see if it works won't work for containerized services that are DNAT-ed (plus, that would be racy) - inspecting iptables instead (or in addition to) may work for containers, but this depends on how networking has been set (and yes, it is also racy) Our approach here is optimistic: tests are responsible for calling Acquire and Release |
Click to show internal directories.
Click to hide internal directories.