You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 24, 2020. It is now read-only.
These three doesn't require much changes to existing rkt. So I put them altogether.
rkt app list
rkt app list will provide minimum information on what are running in the pod, and their states.
More detailed information can be retrieved by rkt app status in further.
The example output for rkt app list would be:
$ rkt app list <pod-uuid>
NAME STATE
appName1 running
appName2 exited
...
The rkt app list and rkt app status could be implemented by aliasing today's rkt list and 'rkt status`. Which means it does not have to implement new stage1 entrypoints.
Some discussion points:
Should we return as key value pairs like I listed above, or should we return a json structured file? Or both, by providing an optional --format=json flag.
Uh oh!
There was an error while loading. Please reload this page.
This follows #2932
These three doesn't require much changes to existing rkt. So I put them altogether.
rkt app list
rkt app list
will provide minimum information on what are running in the pod, and their states.More detailed information can be retrieved by
rkt app status
in further.The example output for
rkt app list
would be:rkt app status
The
rkt app list
andrkt app status
could be implemented by aliasing today'srkt list
and 'rkt status`. Which means it does not have to implement new stage1 entrypoints.Some discussion points:
--format=json
flag.rkt app exec
This is equivalent to
cc @euank @tmrts @s-urbaniak
The text was updated successfully, but these errors were encountered: