Bot releases are hidden (Show)
Published by dcantah about 3 years ago
Published by dcantah about 3 years ago
github.com/microsoft/hcsshim/hcn
package where logs were being generated on every invocation of any of the hcn.XSupported
methods or hcn.GetSupportedFeatures
. There's now only one log printed on the first invocation of any of the methods.GetCachedSupportedFeatures
to the github.com/microsoft/hcsshim/hcn
package. This optimizes for scenarios where multiple calls are made to check if certain features are supported by caching the very first result from HCN.GetHNSEndpointStats
function to the github.com/microsoft/hcsshim/
package. This allows statistics about the hns endpoint to be queried.Published by kevpar over 3 years ago
github.com/Microsoft/hcsshim
package where IsAlreadyStopped
and IsNotExist
would erroneously return true
for ERROR_PROC_NOT_FOUND
(#1065).Published by dcantah over 3 years ago
Shim
Published by dcantah over 3 years ago
Published by katiewasnothere over 3 years ago
Published by kevpar over 3 years ago
delete
action, it will look for and log panic.log in the bundle directorypkg/ociwclayer
package with support for working with Windows container layersPublished by dcantah almost 4 years ago
Published by dcantah almost 4 years ago
Published by dcantah almost 4 years ago
Published by dcantah almost 4 years ago
SetJobCompartmentId
binding and expose CompartmentId
on hns Namespace
object.Published by kevpar about 4 years ago
Published by dcantah over 4 years ago
Published by dcantah over 4 years ago
Published by jterry75 almost 5 years ago
hcsshim
for Docker
hcsshim
v1
HCS
syscall overhead.hcn
L4ProxyPolicySetting
CompartmentID
field.NatFlags
to PortMappings
.containerd-shim-runhcs-v1.exe
for containerd
There are significant changes since the last official release of hcsshim.
The most important change is that we are officially deprecating runhcs.exe
as the containerd
runtime of choice and have removed the v1
runtime bindings for it from containerd
. It is now expected that for containerd
on Windows you use Runtime V2 shim implemented in the cmd/containerd-shim-runhcs-v1
section of the repo.
containerd-shim-runhcs-v1.exe
With the move to containerd
the containerd-shim-runhcs-v1.exe
binary now replaces all OS level interaction with the gRPC interface implemented by the Runtime V2 interface as defined by containerd
. This allows us to fully implement Windows process and Hyper-V containers on RS1+ with support for Windows v2 containers as well as LCOW on RS5+ releases of Windows.
The implementation is as follows for your HOST OS version of Windows:
RS1 - RS4 | RS5+ | |
---|---|---|
Windows Process Container | v1 (Argon) | v2 |
Windows Hyper-V (Server) Container | v1 (Xenon) | v2 |
LCOW | Not Supported | v2 |
The main difference with Windows v2 containers and LCOW v2 is the ability of the shim to support true Kubernetes pod
's. On Windows this means a shared network namespace for process containers in the pod
. For Windows hypervisor (including LCOW) containers it additionally means shared processor, memory, and storage for all containers in the pod
within a single UtilityVM
. This single UtilityVM
provides higher performance and density while also providing greater lifetime guarantees for the set.
Published by lowenna over 5 years ago
create-scratch
utility VM (256MB/1 VPMem device)Published by jterry75 over 5 years ago
runhcs.exe
path to exec
to the path of the calling binary. In practice this is always a containerd shim
and the deployment places them in the same folder. This allows a user who has not placed containerd
in its path to avoid seeing this failure.Published by jterry75 over 5 years ago
mount.Type
"physical-disk" and "virtual-disk" for WCOW and LCOW.
m := &oci.Mount{
Type: "physical-disk",
Source: "\\\\.\\PHYSICALDRIVE1",
Destination: "C:\\test" // LCOW '/mnt/test'
m := &oci.Mount{
Type: "virtual-disk",
Source: "C:\\test.vhdx", // OR 'C:\\test.vhd'
Destination: "C:\\test" // LCOW '/mnt/test'
ole32
to improve process activationTerminateOnLastHandleClosed
for all UVM activation's to guarantee resource cleanup on runhcs.exe
exit.StopOnReset
for all UVM activation's so that the guest VM does not try to restart on reset.rootfs.vhd
when present over initrd.img
by default.>= 18286
add support to LCOW for booting directly from the kernel (compressed or uncompressed)logrus
messages to ETW for all runhcs.exe
invocations.uvmboot.exe
tool for creating/starting/measuring performance of various LCOW configurations. This does not activate any containers but can be useful for creating/testing different LCOW options with various HCS/kernel features.ReadOnly
when OCI opts ro
is set.TERM
, KILL
, 15
, 9
signals for Windows container Kill requests using Unix semantics.Published by jterry75 almost 6 years ago
exec.LookPath
results for runhcs.exe
when using the go-runhcs
pkg. This can lead to about 15 ms savings per runhcs.exe
command.io.microsoft.virtualmachine.computetopology.memory.sizeinmb
allowing UVM override of memory size at activation if not using WindowsMemoryResources.Limit
.io.microsoft.virtualmachine.computetopology.processor.count
allowing UVM override of CPU count at activation if not using WindowsCPUResources.Count
.io.microsoft.virtualmachine.lcow.preferredrootfstype
allowing UVM override of LCOW UVM boot. Values (default: initrd
, vhd
).logrus.WithFields
rather than encoding the values in the message to make it easier for post processing logs.--owner
flag to the container/uvm activation.ARM32
builds causing an build overflow.Published by jterry75 almost 6 years ago
Performance Improvements:
exec.LookPath
results for runhcs.exe
when using the go-runhcs
pkg. This can lead to about 15 ms
savings per runhcs.exe
command.