Files
linuxkit/projects
Ian Campbell 425553d390 kubernetes: better tolerate bad contents of /etc/kubeadm/kube-system.init/
Specifically ignore present-but-empty files entirely and ignore (but log)
failure to apply any one file.

Ignoring an empty file is useful because it means you can clobber a file which
might be referenced from an images binds without needing to override those
binds (since that generally means duplicating the whole lot which is annoying).

Ignoring any failures to apply means the rest gets applied and the rest of the
script (including untaint and the stamp file creation) still happen, resulting
in a system where the admin just has to address the failures rather than the
remaining updates. We touch a file to indicate failure generally plus one to
indicate the specific yaml which failed to apply.

Signed-off-by: Ian Campbell <ijc@docker.com>
2017-11-10 14:50:11 +00:00
..
2017-10-20 04:54:53 -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.