Files
linuxkit/projects
Ian Campbell 9397b9480a kubernetes: populate host CNI paths by binding from kubernetes service.
Kubernetes assumes (for now) that various paths are valid at the host level to
be mounted into containers, including /opt/cni and /etc/cni.

We cannot (easily) use symlinks here because the weave.yml mounts /opt and /etc
rather than /opt/cni and /etc/cni (this seems likely to be common pattern). So
if /etc/cni were a symlink to the persistent disk (under /var/lib) then it will
be dangling link within the weave container.

So add bind mounts to the runtime configuration of the kubernetes image. This
also means we must create the target mount points in the yml.

Signed-off-by: Ian Campbell <ijc@docker.com>
2017-09-18 14:25:54 +01:00
..
2017-09-14 17:21:01 +01:00
2017-09-14 17:21:01 +01:00
2017-09-14 17:21:01 +01:00
2017-09-14 11:47:38 +01:00
2017-09-14 11:47:38 +01:00
2017-09-14 17:21:01 +01:00
2017-07-20 16:05:03 -04:00

Projects

We aim to provide a set of open spaces for collaboration to help move projects towards production. Projects should usually at a minimum provide a README of how to get started using the project with Moby, and a roadmap document explaining what the aims are and how to contribute. Most projects will probably provide a way to run the project in a custom Moby build in its current state, which ideally will be integrated in the Moby CI so there are checks that it builds and runs. Over time we hope that many projects will graduate into the recommended production defaults, but other projects may remain as ongoing projects, such as kernel hardening.

If you want to create a project, please submit a pull request to create a new directory here.

Current projects

Current projects not yet documented

  • VMWare support (VMWare)
  • ARM port and secure boot integration (ARM)

Completed projects

  • aws/: AWS support was merged into mainline in #1964.
  • wireguard/: WireGuard is now part of the default LinuxKit kernel and package set.