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

platforms: update format for platform specifier

Browse Source 
Signed-off-by: Stephen J Day <stephen.day@docker.com>
This commit is contained in:
Stephen J Day 2017-09-13 11:41:45 -07:00
parent 94f6be5f10
commit 775f7cea47
No known key found for this signature in database
GPG Key ID: 67B3DED84EDC823F
1 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
platforms/platforms.go
View File

@ -49,8 +49,9 @@
// While the OCI platform specifications provide a tool for components to
// specify structured information, user input typically doesn't need the full
// context and much can be inferred. To solve this problem, we introduced
// "specifiers". A specifier has the format `<os|arch>[/<arch>[/<variant>]]`.
// The user can provide either the operating system or the architecture or both.
// "specifiers". A specifier has the format
// `<os>|<arch>|<os>/<arch>[/<variant>]`. The user can provide either the
// operating system or the architecture or both.
//
// An example of a common specifier is `linux/amd64`. If the host has a default
// of runtime that matches this, the user can simply provide the component that
@ -130,10 +131,10 @@ func (m *matcher) String() string {
// Parse parses the platform specifier syntax into a platform declaration.
//
// Platform specifiers are in the format <os|arch>[/<arch>[/<variant>]]. The
// minimum required information for a platform specifier is the operating system
// or architecture. If there is only a single string (no slashes), the value
// will be matched against the known set of operating systems, then fall
// Platform specifiers are in the format `<os>|<arch>|<os>/<arch>[/<variant>]`.
// The minimum required information for a platform specifier is the operating
// system or architecture. If there is only a single string (no slashes), the
// value will be matched against the known set of operating systems, then fall
// back to the known set of architectures. The missing component will be
// inferred based on the local environment.
//