Skip to main content
porter app contains commands for managing and interacting with your applications.

Prerequisites


porter app run

Execute a command in your application’s container. By default, this spins up an ephemeral copy of your container that is deleted when the command completes. Usage:
porter app run [APP_NAME] [flags] -- [COMMAND] [args...]
Options:
FlagShortDescription
--existing-eConnect to an existing running container instead of spinning up a new one
--jobTrigger a manual run of the specified job
--waitWait for the job to complete before exiting (used with --job)
--allow-concurrentAllow concurrent runs for jobs that normally restrict it
--serviceSpecify which service to connect to
porter app run my-app -- bash
If bash isn’t available in your container, try sh for a similar interactive experience.

porter app logs

Stream real-time logs or view historical logs from your application. Usage:
porter app logs [APP_NAME] [flags]
Options:
FlagDescription
--serviceFilter logs by service name
--searchSearch for a specific string in the logs
--revisionStream logs from a specific revision
Historical Log Options:
FlagDescription
--sincePull logs from the specified duration (e.g., 12h, 30m)
--fromStart timestamp for historical logs (RFC3339 format)
--toEnd timestamp for historical logs (RFC3339 format)
--limitNumber of lines to return (default: 100)
--newest-firstReturn newest logs first (default: true)
porter app logs my-app
By default, the command streams new logs. Setting --since or --from/--to switches to pulling historical logs.

porter app build

Build a new container image for an app based on its existing build settings. Any build setting can be overridden with flags. Usage:
porter app build [APP_NAME] [flags]
Options:
FlagDescription
--build-contextOverride the build context directory
--dockerfileOverride the Dockerfile path
--tagSpecify a custom image tag
--methodBuild method (docker or pack)
--builderBuilder image for buildpack builds
--buildpacksComma-separated list of buildpacks
porter app build my-app

porter app push

Push a container image to the default registry for the app. Can be used with porter app build to build and push as discrete steps. Usage:
porter app push [APP_NAME] [flags]
Options:
FlagDescription
--tagSpecify the image tag to push (defaults to current branch HEAD)
porter app push my-app

porter app update

Update an application with the provided configuration without building a new image. This is similar to updating the app in the Porter dashboard. Usage:
porter app update [APP_NAME] [flags]
Options:
FlagShortDescription
--file-fPath to the porter.yaml configuration file
--tagUpdate the image tag
porter app update my-app -f porter.yaml
This command differs from porter apply in that it only updates the app configuration without attempting to build a new image.

porter app update-tag

Update the image tag for an application. This is functionally equivalent to running porter apply or porter app update with the --tag flag. Usage:
porter app update-tag [APP_NAME] [flags]
Options:
FlagDescription
--tagThe new image tag to deploy (required)
porter app update-tag my-app --tag abc123def

porter app yaml

Export the current Porter YAML configuration for an application. Useful for bootstrapping a porter.yaml file or inspecting the current configuration. Usage:
porter app yaml [APP_NAME]
porter app yaml my-app
Redirect the output to create a porter.yaml file: porter app yaml my-app > porter.yaml

porter app list

List all applications in the current project and cluster. Usage:
porter app list