Remove kpod launch example code
We now have actual kpod code, so no reason to have a not implemented feature. Especially when we don't intend to create kpod launch. Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
This commit is contained in:
parent
73c5285260
commit
0bd5f6cebc
6 changed files with 1 additions and 72 deletions
|
@ -1,16 +0,0 @@
|
|||
package main
|
||||
|
||||
import (
|
||||
"fmt"
|
||||
|
||||
"github.com/urfave/cli"
|
||||
)
|
||||
|
||||
// TODO implement
|
||||
var launchCommand = cli.Command{
|
||||
Name: "launch",
|
||||
Usage: "launch a pod",
|
||||
Action: func(context *cli.Context) error {
|
||||
return fmt.Errorf("this functionality is not yet implemented")
|
||||
},
|
||||
}
|
|
@ -23,7 +23,6 @@ func main() {
|
|||
|
||||
app.Commands = []cli.Command{
|
||||
imagesCommand,
|
||||
launchCommand,
|
||||
rmiCommand,
|
||||
tagCommand,
|
||||
versionCommand,
|
||||
|
|
|
@ -68,14 +68,6 @@ _kpod_rmi() {
|
|||
esac
|
||||
}
|
||||
|
||||
_kpod_launch() {
|
||||
local options_with_args="
|
||||
"
|
||||
local boolean_options="
|
||||
"
|
||||
_complete_ "$options_with_args" "$boolean_options"
|
||||
}
|
||||
|
||||
_kpod_version() {
|
||||
local options_with_args="
|
||||
"
|
||||
|
@ -110,7 +102,6 @@ _kpod_kpod() {
|
|||
"
|
||||
commands="
|
||||
images
|
||||
launch
|
||||
rmi
|
||||
tag
|
||||
version
|
||||
|
|
|
@ -1,42 +0,0 @@
|
|||
% kpod(8) # kpod-launch - Simple management tool for pods and images
|
||||
% Dan Walsh
|
||||
% SEPTEMBER 2016
|
||||
# NAME
|
||||
kpod-launch - Launch a new pod
|
||||
|
||||
# SYNOPSIS
|
||||
**kpod launch**
|
||||
[**--help**|**-h**]
|
||||
|
||||
# DESCRIPTION
|
||||
Launch a container process in a new pod. **kpod launch** starts a process with
|
||||
its own file system, its own networking, and its own isolated process tree.
|
||||
The IMAGE which starts the process may define defaults related to the process
|
||||
that will be launch in the pod, the networking to expose, and more, but
|
||||
**kpod launch** gives final control to the operator or administrator who
|
||||
starts the pod from the image. For that reason **kpod launch** has more
|
||||
options than any other kpod commands.
|
||||
|
||||
If the IMAGE is not already loaded then **kpod launch** will pull the IMAGE, and
|
||||
all image dependencies, from the repository in the same way launching **kpod
|
||||
pull** IMAGE, before it starts the container from that image.
|
||||
|
||||
**kpod [GLOBAL OPTIONS]**
|
||||
|
||||
**kpod [GLOBAL OPTIONS] launch [OPTIONS]**
|
||||
|
||||
# GLOBAL OPTIONS
|
||||
|
||||
**--help, -h**
|
||||
Print usage statement
|
||||
|
||||
# COMMANDS
|
||||
|
||||
## launch
|
||||
Launch a pod
|
||||
|
||||
# SEE ALSO
|
||||
kpod(1), crio(8), crio.conf(5)
|
||||
|
||||
# HISTORY
|
||||
Dec 2016, Originally compiled by Dan Walsh <dwalsh@redhat.com>
|
|
@ -12,7 +12,7 @@ Assigns a new alias to an image in a registry. An alias refers to the entire im
|
|||
|
||||
**kpod [GLOBAL OPTIONS]**
|
||||
|
||||
**kpod [GLOBAL OPTIONS] launch [OPTIONS]**
|
||||
**kpod [GLOBAL OPTIONS] tag [OPTIONS]**
|
||||
|
||||
# GLOBAL OPTIONS
|
||||
|
||||
|
|
|
@ -32,9 +32,6 @@ has the capability to debug pods/images created by crio.
|
|||
## images
|
||||
List images in local storage
|
||||
|
||||
## launch
|
||||
Launch a pod
|
||||
|
||||
## rmi
|
||||
Removes one or more locally stored images
|
||||
|
||||
|
|
Loading…
Reference in a new issue