You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/actions/how-tos/manage-runners/larger-runners/use-custom-images.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,6 +44,7 @@ To create a custom image, you must first set up an image-generation runner. When
44
44
***Platform**: Select a supported platform that matches the platform of the image you plan to create (Linux x64, Linux ARM64, or Windows x64).
45
45
***Image**: Select an image to build on, then enable the checkbox **Enable this runner to generate custom images**.
46
46
* You can start from a {% data variables.product.github %}-owned image or choose a base image to start from a clean OS.
47
+
* You can start from an existing custom image as the base, enabling layered image workflows.
47
48
* For ARM64 platforms, you can also select an ARM-maintained image with preinstalled tooling.
48
49
***Runner group**: Select the group for your runner to be a member of. Once the custom image is created, only runners in this runner group can generate new versions of that image.
49
50
@@ -139,6 +140,12 @@ If you specify an older major version in the YAML (for example, version: 1.* whe
139
140
> [!NOTE]
140
141
> {% data variables.actions.github_hosted_larger_runner %} creation does not support wildcards in image version selection.
141
142
143
+
## Expiration for images built from custom images
144
+
145
+
When a custom image is built from another custom image, the derived image inherits the expiration timeline of its base image. The maximum version age is calculated from when the base custom image was built, not when the derived image was created.
146
+
147
+
For example, if Custom Image A is built on Day 2 and Custom Image B is built from A on Day 4 with a 7-day maximum version age policy, both A and B expire on Day 9.
148
+
142
149
## Billing and storage for custom images
143
150
144
151
Jobs that use custom images are billed at the same per-minute rate as the {% data variables.actions.hosted_runner %} that uses the image. Storage for custom images is billed separately through {% data variables.product.prodname_actions %} storage.
intro: 'Actions policies let you govern how {% data variables.product.prodname_actions %} workflows run across organizations and repositories in your enterprise, starting with workflow execution protections.'
5
+
versions:
6
+
ghec: '*'
7
+
contentType: concepts
8
+
---
9
+
10
+
{% data reusables.actions.actions-policies-preview-note %}
11
+
12
+
{% data reusables.actions.actions-policies-about-body %}
13
+
14
+
## Next steps
15
+
16
+
To configure workflow execution protections for your enterprise, including setting up event and actor rules, see [AUTOTITLE](/admin/enforcing-policies/enforcing-policies-for-your-enterprise/actions-policies/workflow-execution-protections).
intro: 'Actions policies let you govern how {% data variables.product.prodname_actions %} workflows run across organizations and repositories in your enterprise.'
intro: 'Workflow execution protections let you control who can trigger {% data variables.product.prodname_actions %} workflows and which events are permitted to run them across your enterprise.'
5
+
versions:
6
+
ghec: '*'
7
+
contentType: how-tos
8
+
---
9
+
10
+
{% data reusables.actions.workflow-execution-protections-preview-note %}
11
+
12
+
{% data reusables.actions.workflow-execution-protections-body %}
13
+
14
+
## Configuring workflow execution protections
15
+
16
+
You configure workflow execution protections in the new **Policies** section of your {% data variables.product.prodname_actions %} settings. This **Policies** section is separate from your existing **General** settings.
17
+
18
+
{% data reusables.enterprise-accounts.access-enterprise %}
19
+
{% data reusables.enterprise-accounts.policies-tab %}
20
+
{% data reusables.enterprise-accounts.actions-tab %}
21
+
1. Click **Policies**.
22
+
1. Create a ruleset, then add your event and actor rules.
23
+
1. Choose whether the ruleset is active or in evaluate mode, then save your changes.
intro: 'Actions policies let you govern how {% data variables.product.prodname_actions %} workflows run across repositories in your organization, starting with workflow execution protections.'
5
+
versions:
6
+
fpt: '*'
7
+
ghec: '*'
8
+
contentType: concepts
9
+
---
10
+
11
+
{% data reusables.actions.actions-policies-preview-note %}
12
+
13
+
{% data reusables.actions.actions-policies-about-body %}
14
+
15
+
## Next steps
16
+
17
+
To configure workflow execution protections for your organization, including setting up event and actor rules, see [AUTOTITLE](/organizations/managing-organization-settings/actions-policies/workflow-execution-protections).
intro: 'Workflow execution protections let you control who can trigger {% data variables.product.prodname_actions %} workflows and which events are permitted to run them across your organization.'
5
+
versions:
6
+
fpt: '*'
7
+
ghec: '*'
8
+
contentType: how-tos
9
+
---
10
+
11
+
{% data reusables.actions.workflow-execution-protections-preview-note %}
12
+
13
+
{% data reusables.actions.workflow-execution-protections-body %}
14
+
15
+
## Configuring workflow execution protections
16
+
17
+
You configure workflow execution protections in the new **Policies** section of your {% data variables.product.prodname_actions %} settings. This **Policies** section is separate from your existing **General** settings.
18
+
19
+
{% data reusables.profile.access_org %}
20
+
{% data reusables.profile.org_settings %}
21
+
1. In the left sidebar, under **Actions**, click **Policies**.
22
+
1. Create a ruleset, then add your event and actor rules.
23
+
1. Choose whether the ruleset is active or in evaluate mode, then save your changes.
0 commit comments