github/containerd
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 2 Wiki Activity

fix-grammar-mistake

Browse Source 
Signed-off-by: chentanjun <2799194073@qq.com>
This commit is contained in:
chentanjun 2019-08-28 09:56:57 +08:00
parent 309617819b
commit 92a5b08a68
6 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
containers/containers.go
View File

@ -49,7 +49,7 @@ type Container struct {
// This property is required and immutable. // This property is required and immutable.
Runtime RuntimeInfo Runtime RuntimeInfo
// Spec should carry the the runtime specification used to implement the // Spec should carry the runtime specification used to implement the
// container. // container.
// //
// This field is required but mutable. // This field is required but mutable.

2
docs/namespaces.md
View File

@ -64,7 +64,7 @@ Note that currently only these two labels are used to configure the defaults and
If we need to inspect containers, images, or other resources in various namespaces the `ctr` tool allows you to do this. If we need to inspect containers, images, or other resources in various namespaces the `ctr` tool allows you to do this.
Simply set the `--namespace,-n` flag on `ctr` to change the namespace. If you do not provide a namespace, `ctr` client commands Simply set the `--namespace,-n` flag on `ctr` to change the namespace. If you do not provide a namespace, `ctr` client commands
will all use the the default namespace, which is simply named "`default`". will all use the default namespace, which is simply named "`default`".
```bash ```bash
> sudo ctr -n docker tasks > sudo ctr -n docker tasks

2
log/context.go
View File

@ -30,7 +30,7 @@ var (
// messages. // messages.
G = GetLogger G = GetLogger
// L is an alias for the the standard logger. // L is an alias for the standard logger.
L = logrus.NewEntry(logrus.StandardLogger()) L = logrus.NewEntry(logrus.StandardLogger())
) )

4
oci/spec_opts.go
View File

@ -118,7 +118,7 @@ func WithDefaultSpecForPlatform(platform string) SpecOpts {
} }
} }
// WithSpecFromBytes loads the the spec from the provided byte slice. // WithSpecFromBytes loads the spec from the provided byte slice.
func WithSpecFromBytes(p []byte) SpecOpts { func WithSpecFromBytes(p []byte) SpecOpts {
return func(_ context.Context, _ Client, _ *containers.Container, s *Spec) error { return func(_ context.Context, _ Client, _ *containers.Container, s *Spec) error {
*s = Spec{} // make sure spec is cleared. *s = Spec{} // make sure spec is cleared.
@ -628,7 +628,7 @@ func WithUserID(uid uint32) SpecOpts {
} }
// WithUsername sets the correct UID and GID for the container // WithUsername sets the correct UID and GID for the container
// based on the the image's /etc/passwd contents. If /etc/passwd // based on the image's /etc/passwd contents. If /etc/passwd
// does not exist, or the username is not found in /etc/passwd, // does not exist, or the username is not found in /etc/passwd,
// it returns error. // it returns error.
func WithUsername(username string) SpecOpts { func WithUsername(username string) SpecOpts {

2
platforms/platforms.go
View File

@ -130,7 +130,7 @@ type Matcher interface {
// specification. The returned matcher only looks for equality based on os, // specification. The returned matcher only looks for equality based on os,
// architecture and variant. // architecture and variant.
// //
// One may implement their own matcher if this doesn't provide the the required // One may implement their own matcher if this doesn't provide the required
// functionality. // functionality.
// //
// Applications should opt to use `Match` over directly parsing specifiers. // Applications should opt to use `Match` over directly parsing specifiers.

2
reports/2017-02-10.md
View File

@ -38,7 +38,7 @@ much smaller interface!
## Bundles Bundles Bundles ## Bundles Bundles Bundles
We spend time talking with people implementing Windows support as well as a few other users. We spend time talking with people implementing Windows support as well as a few other users.
One the the major issues with our current approach was that bundles were a central part of our architecture. One the major issues with our current approach was that bundles were a central part of our architecture.
The content and storage subsystems would produce bundles and the execution subsystem would consume them. The content and storage subsystems would produce bundles and the execution subsystem would consume them.
However, with a bundle being on the filesystem, having this concept does not work as smoothly on Windows However, with a bundle being on the filesystem, having this concept does not work as smoothly on Windows
as it would for Unix platforms. as it would for Unix platforms.