package hcsoci
import "github.com/Microsoft/hcsshim/internal/hcsoci"
Index ¶
- func CreateContainer(ctx context.Context, createOptions *CreateOptions) (_ cow.Container, _ *resources.Resources, err error)
- func GetNamespaceEndpoints(ctx context.Context, netNS string) ([]*hns.HNSEndpoint, error)
- type CreateOptions
Functions ¶
func CreateContainer ¶
func CreateContainer(ctx context.Context, createOptions *CreateOptions) (_ cow.Container, _ *resources.Resources, err error)
CreateContainer creates a container. It can cope with a wide variety of scenarios, including v1 HCS schema calls, as well as more complex v2 HCS schema calls. Note we always return the resources that have been allocated, even in the case of an error. This provides support for the debugging option not to release the resources on failure, so that the client can make the necessary call to release resources that have been allocated as part of calling this function.
func GetNamespaceEndpoints ¶
GetNamespaceEndpoints gets all endpoints in `netNS`
Types ¶
type CreateOptions ¶
type CreateOptions struct { // Common parameters ID string // Identifier for the container Owner string // Specifies the owner. Defaults to executable name. Spec *specs.Spec // Definition of the container or utility VM being created SchemaVersion *hcsschema.Version // Requested Schema Version. Defaults to v2 for RS5, v1 for RS1..RS4 HostingSystem *uvm.UtilityVM // Utility or service VM in which the container is to be created. NetworkNamespace string // Host network namespace to use (overrides anything in the spec) // This is an advanced debugging parameter. It allows for diagnosibility by leaving a containers // resources allocated in case of a failure. Thus you would be able to use tools such as hcsdiag // to look at the state of a utility VM to see what resources were allocated. Obviously the caller // must a) not tear down the utility VM on failure (or pause in some way) and b) is responsible for // performing the ReleaseResources() call themselves. DoNotReleaseResourcesOnFailure bool // ScaleCPULimitsToSandbox indicates that the container CPU limits should be adjusted to account // for the difference in CPU count between the host and the UVM. ScaleCPULimitsToSandbox bool }
CreateOptions are the set of fields used to call CreateContainer(). Note: In the spec, the LayerFolders must be arranged in the same way in which moby configures them: layern, layern-1,...,layer2,layer1,scratch where layer1 is the base read-only layer, layern is the top-most read-only layer, and scratch is the RW layer. This is for historical reasons only.
Source Files ¶
create.go devices.go hcsdoc_lcow.go hcsdoc_wcow.go network.go resources_lcow.go resources_wcow.go
- Version
- v0.8.14
- Published
- Dec 18, 2020
- Platform
- windows/amd64
- Imports
- 32 packages
- Last checked
- 21 minutes ago –
Tools for package owners.