exec command¶

The exec command is used to execute a remote command and wait for it to finish.

Usage¶

user@host:~$ pebble exec --help

Usage: pebble exec [exec-OPTIONS] <command> The exec command runs a remote command and waits for it to finish. The localstdin is sent as the input to the remote process, while the remote stdout andstderr are output locally. To avoid confusion, exec options may be separated from the command and itsarguments using "--", for example: pebble exec --timeout 10s -- echo -n foo bar [exec command options] -w= Working directory to run command in --env= Environment variable to set (in 'FOO=bar' format) --uid= User ID to run command as --user= Username to run command as (user's UID must match uid if both present) --gid= Group ID to run command as --group= Group name to run command as (group's GID must match gid if both present) --timeout= Timeout after which to terminate command --context= Inherit the context of the named service (overridden by -w, --env, --uid/user, --gid/group) -t Allocate remote pseudo-terminal and connect stdout to it (default if stdout is a TTY) -T Disable remote pseudo-terminal allocation -i Interactive mode: connect stdin to the pseudo-terminal (default if stdin and stdout are TTYs) -I Disable interactive mode and use a pipe for stdin

Examples¶

For example, you could use exec to run pg_dump and create a PostgreSQL database backup:

user@host:~$ pebble exec pg_dump mydb

---- PostgreSQL database dump--...

The exec feature uses WebSockets under the hood, and allows you to stream stdin to the process, as well as stream stdout and stderr back. When running pebble exec, you can specify the working directory to run in (-w), environment variables to set (--env), and the user and group to run as (--uid/--user and --gid/--group).

You can also apply a timeout with --timeout, for example:

user@host:~$ pebble exec --timeout 1s -- sleep 3

error: cannot perform the following tasks:- exec command "sleep" (timed out after 1s: context deadline exceeded)