Skip to main content
By default, actions run on the install runner. Setting image executes the action inside a container image you provide.
Container actions are behind the image-backed-actions org feature flag and are off by default. Reach out to Nuon to enable it for your org.

​
Configure it

Add image to the action and configure a step with inline_contents:
actions/db_migrate.toml
Sync it the same way as any other action:
Everything else about the action is unchanged: triggers, timeout (30 minutes maximum), role, enable_kube_config, env_vars, and templating all behave exactly as they do when the action runs on the runner. See Configure actions.

​
Choosing an image

You can use publically hosted images or component images from your Nuon app config.

​
A public reference

actions/db_migrate.toml

​
A private image

Publish the image as a container image component and point image at its image.ref output:
actions/db_migrate.toml
Use the component’s image.ref output, not image.repository and image.tag. A bare repository:tag is rejected with not digest-pinned.

​
Building the image

Nuon does not modify the image. It must include every tool and dependency the action needs; the runner toolchain is not available inside the container.