Little helper to run CNCF's k3s in Docker

docker kubernetes go k3s rancher cluster k3d

History

iwilltry42 c688391549 vendor update including kubernetes, docker, containerd, etc.		4 years ago
..
computestorage	vendor update including kubernetes, docker, containerd, etc.	4 years ago
internal	vendor update including kubernetes, docker, containerd, etc.	4 years ago
osversion	vendor update including kubernetes, docker, containerd, etc.	4 years ago
.gitattributes	vendor update including kubernetes, docker, containerd, etc.	4 years ago
.gitignore	update modules	5 years ago
.gometalinter.json	update modules	5 years ago
CODEOWNERS	vendor update including kubernetes, docker, containerd, etc.	4 years ago
LICENSE	update modules	5 years ago
Protobuild.toml	dependencies: update docker dependencies to fix issues with failing windows builds introduced by the usage of the archive package	4 years ago
README.md	dependencies: update docker dependencies to fix issues with failing windows builds introduced by the usage of the archive package	4 years ago
appveyor.yml	[Feature] Registry for v4 & Restructure Cluster Creation (#334 )	4 years ago
container.go	dependencies: update docker dependencies to fix issues with failing windows builds introduced by the usage of the archive package	4 years ago
errors.go	update modules	5 years ago
functional_tests.ps1	update modules	5 years ago
go.mod	vendor update including kubernetes, docker, containerd, etc.	4 years ago
go.sum	vendor update including kubernetes, docker, containerd, etc.	4 years ago
hcsshim.go	update modules	5 years ago
hnsendpoint.go	dependencies: update docker dependencies to fix issues with failing windows builds introduced by the usage of the archive package	4 years ago
hnsglobals.go	update modules	5 years ago
hnsnetwork.go	update modules	5 years ago
hnspolicy.go	dependencies: update docker dependencies to fix issues with failing windows builds introduced by the usage of the archive package	4 years ago
hnspolicylist.go	update modules	5 years ago
hnssupport.go	update modules	5 years ago
interface.go	update modules	5 years ago
layer.go	dependencies: update docker dependencies to fix issues with failing windows builds introduced by the usage of the archive package	4 years ago
process.go	dependencies: update docker dependencies to fix issues with failing windows builds introduced by the usage of the archive package	4 years ago
zsyscall_windows.go	update modules	5 years ago

README.md

hcsshim

This package contains the Golang interface for using the Windows Host Compute Service (HCS) to launch and manage Windows Containers. It also contains other helpers and functions for managing Windows Containers such as the Golang interface for the Host Network Service (HNS).

It is primarily used in the Moby Project, but it can be freely used by other projects as well.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

We also ask that contributors sign their commits using git commit -s or git commit --signoff to certify they either authored the work themselves or otherwise have permission to use it in this project.

Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Dependencies

This project requires Golang 1.9 or newer to build.

For system requirements to run this project, see the Microsoft docs on Windows Container requirements.

Reporting Security Issues

Security issues and bugs should be reported privately, via email, to the Microsoft Security Response Center (MSRC) at secure@microsoft.com. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Further information, including the MSRC PGP key, can be found in the Security TechCenter.

For additional details, see Report a Computer Security Vulnerability on Technet