Start and wait on an op
if a node isn't running, one will be automatically created
Op reference (either
host/path/repo#tag (since v0.1.19), or
Explicitly pass args to op in format
-a NAME1=VALUE1 -a NAME2=VALUE2
Read in a file of args in yml format
opctl run myop
opctl run -a apiToken="my-token" -a channelName="my-channel" -a msg="hello!" github.com/opspec-pkgs/slack.chat.post-message#0.1.1
If auth w/ the op source fails the cli will (re)prompt for username & password.
in non-interactive terminals, the cli will note that it can't prompt due to being in a non-interactive terminal and exit with a non zero exit code.
Input sources are checked according to the following precedence:
- arg provided via
- arg file (since v0.1.19)
- env var
Inputs which are invalid or missing will result in the cli prompting for them.
in non-interactive terminals, the cli will provide details about the invalid or missing input, note that it's giving up due to being in a non-interactive terminal and exit with a non zero exit code.
- Please provide value for parameter. Name: version Description: version of app being compiled -
When inputs don't meet constraints, the cli will (re)prompt for the input until a satisfactory value is obtained.
All pulled image layers will be cached
Prior to container creation, updates to the referenced image will be pulled and applied.
If checking for or applying updated image layers fails, graceful fallback to cached image layers will occur
All containers created by opctl will be attached to a single managed network.
the network is visible from
docker network lsas
Containers will be removed as they exit.