Unity Runners for Gitea

Gitea Act Runner images with Unity3D installed and additional modules for packaging, building, and testing your Unity3D projects and games.

Built on the work done by GameCI, these images are designed to run your build scripts directly in the container.

Why?

The game-ci/unity-builder action builds your project inside a Docker container. However with the way Gitea works, this causes issues as you end up with docker-in-docker containers which are not entirely stable, have issues with caching, and annoying to manage with files.

Using this image, you are directly able to launch your runner scripts inside the same container that Unity is in.

Tip

You can use either the jobs.<name>.container.image to override the job's current container image, or you can directly add a label to your runner such as:

  - unity-6000.0.35f1-android:docker://lachee/unity-runner:6000.0.35f1-android-runner
  - unity-6000.0.35f1-webgl:docker://lachee/unity-runner:6000.0.35f1-webgl-runner

There is a included script that will automate your labels as a cron job.

Images

A table of available Docker images for Unity CI/CD:

Unity	all	android	ios	linux-il2cpp	mac-mono	webgl	windows-mono
6000.0.35f1	🐳 View 📦 15.66 GB	🐳 View 📦 12.02 GB	🐳 View 📦 10.47 GB	🐳 View 📦 10.37 GB	🐳 View 📦 10.70 GB	🐳 View 📦 11.60 GB	🐳 View 📦 11.07 GB

Included Software

Tools

• Unity3D (as unity-editor)
• Blender 3.4
• CMake
• CURL
• GCC
• Git
• Make
• Zip & Unzip

Language and Runtime

• Bash 5.1.16(1)-release
• Node.js 20.19.5
• Python3 3.10.12
• lib-sqlite3
• libssl

Package Management

• NPM 11.6.0
• PNPM 10.17.0
• pip3 22.0.2

SDKs

• AWS CLI
• Azure SDK

How

... TODO ...

Note

Depending on your size of project, you might find it would randomly fail. This is likely your gitea-runner running out of memory and terminating. I personally found proxmox did this a lot as the memory grew faster than what the host could balloon. I recommend setting 4GB MIN so it always has space to balloon.

Tip

I run a 10GB VM with 500GB just for Unity3D builds. I have a custom unity label to prevent my other runners getting builds.

Uber Image?

There is a experimental UberRunner.dockerfile. However there have been some issues trying to build and host it:

• The image is MASSIVE, totally around 25GB for a single docker image.
  • Unless you precache the image on your runners, it would take a long time downloading each run
• It requires a lot of memory and storage to build
  • GitHub runners cannot build it, they run out of storage
  • My upload speed is terrible, so i cannot upload them
  • Runners tend to run out of memory and kill the process. I had to dedicate building it to my "-large" runners (with 10GB memory & 500GB storage).
• Android requires additional steps so you just end up reinventing the wheel.
• There is no point?
  • Sure you only need one image, but you still have the same storage concerns than lots of smaller images
  • Let docker be smart and cache the layers. Didn't need to make a mega bundle just for better caching
  • If you need everything / weird setups, just run in host mode with unity pre-installed on a VM.
    • It would cache everything for you too!
    • Less hassle having to deal with licensing.