기술 자료

Unity Engine

Download Unity

Unity Engine

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 CPUUbuntu Linux x86_64Windows, macOS, and Arm64 hosts.
EditorHeadless Editor, Unity 6000.7 and later.Unity 6000.6 and earlier, and the Linux Editor with a graphical interface.
Image contentsUnity CLI and OS prerequisites.Preinstalled Editor, Xvfb, test tooling, FFmpeg.
LicensingUnity license from a floating license server.Named user licenses.

Host requirements

The following table lists the host and network requirements:

Requirement

Detail

HostUbuntu Linux x86_64 with Docker Engine 23.0 or later.
CPU and memoryAt least 8 CPU cores and 16 GB of memory.
DiskSpace for the Editor, its modules, and the
Library
folder. An image with the Editor and one module installed is about 6 GB. Each additional module increases the image size.
NetworkAccess to Docker Hub, the Unity download servers, the Unity package registry, and your license server.
LicenseA 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 serverYesThe lease isn't bound to the machine.
Named user licenseNoActivation binds to machine-identifying information, which changes every time a container starts.
Serial-based activation (
-serial
)
NoActivation 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
linux-il2cpp
None.
Linux Dedicated Server
linux-server
None.
Web
webgl
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
android
The Android SDK, NDK, and OpenJDK versions your Editor version expects. Install them with the module through the CLI (
--cm
), or add them to your image and point the Editor at them.
Windows, macOS
windows-coreclr
,
mac-coreclr
CoreCLR only.
iOS, visionOS
ios
,
visionos
Not supported.
ConsolesPlatform modulesNot 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.

Additional resources