github/linuxkit
1
0
Fork 0
mirror of https://github.com/linuxkit/linuxkit.git synced 2025-09-03 16:07:43 +00:00
Code Issues Projects Releases Wiki Activity

More renames to LinuxKit

Browse Source 
Signed-off-by: Justin Cormack <justin.cormack@docker.com>
This commit is contained in:
Justin Cormack
2017-04-14 11:47:24 -05:00
parent 857d8b6448
commit 72c3f9cfa2
22 changed files with 34 additions and 82 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/faq.md
View File

@@ -11,16 +11,16 @@ system is installed, and it would be useful to support this for that use case, a
updater container to control this for people who want to use this.
We generally use external tooling such as [Infrakit](https://github.com/docker/infrakit) or
CloudFormation templates to manage the update process externally from Moby, including
CloudFormation templates to manage the update process externally from LinuxKit, including
doing rolling cluster upgrades to make sure distributed applciations stay up and responsive.
Updates may preserve the state disk used by applications if needed, either on the same physical
node, or by reattaching a virtual cloud volume to a new node.
## What do I need to build Moby?
## What do I need to build LinuxKit?
We have tried to make this as simple as possible, by using containers for the build process, so
you should be able to build Moby on any OSX or Linux laptop; we should have Windows build support
you should be able to build LinuxKit on any OSX or Linux laptop; we should have Windows build support
soon.
## Why not use `systemd`?

2
docs/kernel-patches.md
View File

@@ -91,4 +91,4 @@ rm $KITSRC/kernel/patches-4.9/*
git format-patch -o $KITSRC/kernel/patches-4.9 v4.9.15..HEAD
```
The, create a PR for Moby.
The, create a PR for LinuxKit.

4
docs/yaml.md
View File

@@ -39,8 +39,8 @@ For details of the config for each container, see below.
This section specifies which build components are to be cryptographically verified with
[Docker Content Trust](https://docs.docker.com/engine/security/trust/content_trust/) prior to pulling.
Trust is a central concern in any build system, and Moby's is no exception: Docker Content Trust provides authenticity,
integrity, and freshness guarantees for the components it verifies. The Moby maintainers are responsible for signing
Trust is a central concern in any build system, and LinuxKit's is no exception: Docker Content Trust provides authenticity,
integrity, and freshness guarantees for the components it verifies. The LinuxKit maintainers are responsible for signing
`mobylinux` components, though collaborators can sign their own images with Docker Content Trust or [Notary](https://github.com/docker/notary).
- `image` lists which individual images to enforce pulling with Docker Content Trust.