lizard ssh
Execute a command inside a running service’s VM, streaming its output and returning the remote exit code.
run vs. ssh
lizard run and lizard ssh both execute a command with a service’s context, but they run in different places — know which one you want.
| Command | Runs where | Use for |
|---|---|---|
lizard run | Locally, with the service’s project + service secrets injected | Migrations, seed scripts, local tooling that needs prod config |
lizard ssh | Inside the running service VM | Inspecting the live container, one-off remote commands, debugging |
lizard run shows your local injected copy of the environment, which is usually the same as production — but lizard ssh is authoritative for what the live container actually sees.
Usage
lizard ssh --service <name> -- <command>Examples
Inspect the environment the running app sees
lizard ssh --service api -- envList files in the deployed image
lizard ssh --service api -- ls -la /appCheck the OS in the container
lizard ssh --service api -- cat /etc/os-releaseConfirm a secret landed in the live container
lizard ssh --service api -- env | grep DATABASE_URLSee also
- lizard run — run a command locally with the service’s env injected instead
- Variables — how secrets and references reach a service