Headless Editor in Docker
Build Unity projects in Linux Docker containers on continuous integration (CI) servers and build farms with the Headless Editor.
読み終わるまでの所要時間 2 分最終更新 3日前
Build Unity projects in Linux Docker containers on continuous integration (CI) servers and build farms with the Headless Editor.
Unity publishes a Unity Editor base image, , that contains the Unity CLI and the system packages the Headless Editor needs. You build your own image from it with the Editor version and modules you build for, store that image in your own registry, and run one container per build job.
unity/editor-baseThe Headless Editor is available only for Linux x86_64.
注
Each container needs a Unity license from a floating license server.
Topic | Description |
|---|---|
| Introduction to the Headless Editor in containers | Understand how the Headless Editor runs in a Docker container, what the base image provides, and what the Editor can't do without a display. |
| Build a Unity Editor Docker image | Create a Docker image that adds the Headless Editor and your build target modules to the base image. |
| Build with Unity in a Docker container | Start a container from your Editor image to build a Unity project with a license from a floating license server. |
| Build in a container with GitHub Actions | Run containerized Unity builds from a GitHub Actions workflow on a self-hosted runner. |
| Verify the Unity Editor base image signature | Check that the base image comes from Unity, and keep its signature when you mirror the image. |
| Headless Editor container requirements reference | Find the hosts, Editor versions, licenses, and build targets that you can use to run the Headless Editor in a container. |
| Unity Editor base image tags reference | Find the tags you can use to pin the base image, and learn when Unity moves each tag and publishes a new image. |
| Troubleshooting the Headless Editor in Docker | Solve common issues when you run the Headless Editor in a container. |