Ограничение базового образа для пространств кода

Overview

When you create a codespace, a development container is automatically created on a remote virtual machine. This dev container is created from a Docker image. The image is effectively a template for Docker containers and it determines many aspects of the resulting environment provided by the codespace. For more information, see GitHub Codespaces overview.

You can choose which image you want to use for your codespaces by specifying it in the dev container configuration for a repository. You can do this, for example, by using the image property in the devcontainer.json file.

"image": "mcr.microsoft.com/devcontainers/javascript-node:18",

"image": "mcr.microsoft.com/devcontainers/javascript-node:18",

For more information, see the dev containers specification on the Development Containers website.

Alternatively, you can specify the base image in a Dockerfile. For more information, see Introduction to dev containers.

If you don't specify an image in the dev container configuration for a repository, the default dev container image is used. The default image contains a number of runtime versions for popular languages and commonly used tools. For more information, see Introduction to dev containers.

As an organization owner, you can add a policy to restrict which dev container images can be used for codespaces created within your organization.

If you attempt to create a codespace using a devcontainer.json that specifies an image that is not allowed by the policy, the following message is displayed in GitHub:

The codespace cannot be created because the image specified in your dev container configuration is not allowed. You may need to select a different branch, modify your container configuration, or adjust your organization's policy setting.

Using the CLI, the error message is:

error creating codespace: HTTP 400: Base image 'IMAGE-REFERENCE' is not allowed based on an organization policy set by your organization administrator.

If the image for a codespace is specified in a Dockerfile, and does not match the policy, a codespace is created in recovery mode, using the default recovery container rather than the specified image. A message to this effect is included at the end of the creation log. For more information about the creation log, see GitHub Codespaces logs.

Setting organization-wide and repository-specific policies

When you create a policy you choose whether it applies to all repositories in your organization, or only to specified repositories. If you set an organization-wide policy then any policies you set for individual repositories must fall within the restriction set at the organization level. Adding policies makes the choice of image more, not less, restrictive.

For example, you could create an organization-wide policy that restricts the base image to any of ten specified images. You can then set a policy for Repository A that restricts the image to a subset of just two of the images specified at the organization level. Specifying additional images for Repository A will have no effect because these images are not specified in the organization-level policy. If you add an organization-wide policy, you should set it to the largest choice of images that will be available for any repository in your organization. You can then add repository-specific policies to further restrict the choice.

Adding a policy to define the allowed images

1. In the upper-right corner of GitHub, select your profile photo, then click Your organizations.

2. Next to the organization, click Settings.

3. In the "Code, planning, and automation" section of the sidebar, select Codespaces then click Policies.

4. On the "Codespaces policies" page, click Create Policy.

5. Enter a name for your new policy.

6. Click Add constraint and choose Base images.

7. Click to edit the constraint.

8. In the "Allowed values" field, enter the image reference of the Docker image you want to allow.

   

   You can use the * wildcard as the last character of the image reference to match all images that start with the same reference to the left of the wildcard. For example, mcr.microsoft.com/devcontainers/*.

9. Click to add the value.

10. If required, repeat the previous two steps to add more image references.

    When you add multiple image references, if an image reference specified in the dev container configuration of a repository does not match any of the references in a policy that applies to the repository, you will not be able to create codespaces for that repository.

11. Click outside of the dialog box to close it.

12. By default the policy is set to apply to all repositories, if you want it to apply only to some of the repositories in your organization, click All repositories and then click Selected repositories in the dropdown menu.

    

    Note

    If you're adding a constraint to an existing policy that already contains the "Maximum codespaces per user" constraint, you won't be able to apply the policy to selected repositories. This is because the "Maximum codespaces per user" constraint always applies to all repositories in the organization.

    With Selected repositories selected:

    1. Click .

       

    2. Select the repositories you want this policy to apply to.

    3. At the bottom of the repository list, click Select repositories.

       

13. If you want to add another constraint to the policy, click Add constraint and choose another constraint. For information about other constraints, see:

    • Restricting access to machine types
    • Restricting the number of organization-billed codespaces a user can create
    • Restricting the visibility of forwarded ports
    • Restricting the idle timeout period
    • Restricting the retention period for codespaces

14. After you've finished adding constraints to your policy, click Save.

The policy is applied when anyone attempts to create a new codespace that is billable to your organization. The base image constraint does not affect existing codespaces, either active or stopped.

Editing a policy

You can edit an existing policy. For example, you may want to add or remove constraints to or from a policy.

1. Display the "Codespaces policies" page. For more information, see Adding a policy to define the allowed images.
2. Click the name of the policy you want to edit.
3. Beside the "Base images" constraint, click .
4. Add or remove image references.
5. Click Save.

Deleting a policy

1. Display the "Codespaces policies" page. For more information, see Adding a policy to define the allowed images.

2. Click to the right of the policy you want to delete.