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.
읽는 시간 3분최근 업데이트: 10일 전
Find the hosts, Editor versions, licenses, and build targets that you can use to run the Headless Editor in a container.
Use these tables to check that your hosts, licenses, and projects can run the Headless Editor in a container before you build an Editor image. For more information about how the Editor and image work, refer to Introduction to the Headless Editor in containers.
Supported configurations
The following table lists what the container setup supports:
Area | Supported | Not supported |
|---|---|---|
| Host OS and CPU | Ubuntu Linux x86_64 | Windows, macOS, and Arm64 hosts. |
| Editor | Headless Editor, Unity 6000.7 and later. | Unity 6000.6 and earlier, and the Linux Editor with a graphical interface. |
| Image contents | Unity CLI and OS prerequisites. | Preinstalled Editor, Xvfb, test tooling, FFmpeg. |
| Licensing | Unity license from a floating license server. | Named user licenses. |
Host requirements
The following table lists the host and network requirements:
Requirement | Detail |
|---|---|
| Host | Ubuntu Linux x86_64 with Docker Engine 23.0 or later. |
| CPU and memory | At least 8 CPU cores and 16 GB of memory. |
| Disk | Space for the Editor, its modules, and the |
| Network | Access to Docker Hub, the Unity download servers, the Unity package registry, and your license server. |
| License | A Unity license on a floating license server the container can reach. |
Licensing options
The following table lists which licensing options work in a container:
Licensing option | Works in a container | Reason |
|---|---|---|
| Unity license from a floating license server | Yes | The lease isn't bound to the machine. |
| Named user license | No | Activation binds to machine-identifying information, which changes every time a container starts. |
Serial-based activation ( | No | Activation binds to the machine, as with a named user license. |
Build target support
The following table lists each build target's module ID for the Unity CLI and the extra setup required for your image:
Target | Module ID | Notes |
|---|---|---|
| Linux Standalone | | None. |
| Linux Dedicated Server | | None. |
| Web | | Install FFmpeg. On Linux, the Editor uses FFmpeg to encode audio clips to AAC, which is required for Web browser compatibility. Unity can't distribute FFmpeg in the image for licensing reasons. The Unity Editor base image includes Python 3, which Web builds require. |
| Android | | The Android SDK, NDK, and OpenJDK versions your Editor version expects. Install them with the module through the CLI ( |
| Windows, macOS | | CoreCLR only. |
| iOS, visionOS | | Not supported. |
| Consoles | Platform modules | Not supported. |
Web isn't the only build target that needs FFmpeg. On Linux, any import that encodes audio to AAC needs it, including imports during Edit mode and Play mode tests. If any of your audio clips import as AAC, install FFmpeg for every build target.