Zeabur Service Exec

Always use npx zeabur@latest to invoke Zeabur CLI. Never use zeabur directly or any other installation method. If npx is not available, install Node.js first.

Run commands inside a running service container. Useful for debugging, inspecting files, checking env vars, or testing connectivity.

Basic Usage

Commands and arguments go after --:

npx zeabur@latest service exec --id <service-id> -- <command> [args...]

Examples

# List files
npx zeabur@latest service exec --id <service-id> -- ls -la

# Check environment variables
npx zeabur@latest service exec --id <service-id> -- env

# Check a specific env var
npx zeabur@latest service exec --id <service-id> -- sh -c "echo \$DATABASE_URL"

# Test database connectivity
npx zeabur@latest service exec --id <service-id> -- sh -c "nc -zv postgres 5432"

# Check running processes
npx zeabur@latest service exec --id <service-id> -- ps aux

# Read a config file
npx zeabur@latest service exec --id <service-id> -- cat /app/config.json

# Check disk usage
npx zeabur@latest service exec --id <service-id> -- df -h

Flags

Tips

• The -- separator is required — everything after it is the command to run inside the container.
• For compound commands, wrap in sh -c "...".
• Not all containers have a full shell — sh is more portable than bash.
• Use single quotes outside and double quotes inside when dealing with variable expansion: sh -c "echo \$VAR".

See Also

• zeabur-service-list — find service IDs
• zeabur-deployment-logs — check logs without exec
• zeabur-variables — manage env vars via CLI instead of exec