question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

no space left on device

See original GitHub issue
Run webbertakken/unity-builder@v2.0-aplha-5
  with:
    projectPath: cs2019/cs2019_pc
    unityVersion: 2020.2.1f1
    targetPlatform: Android
    allowDirtyBuild: true
    kubeContainerMemory: 800M
    kubeContainerCPU: 0.25
    kubeVolumeSize: 5Gi
    versioning: Semantic
    androidAppBundle: false
  env:
    UNITY_LICENSE: ***
Warning: From https://github.com/matrix3d/unitystudy
 * [new branch]        add-license-1 -> origin/add-license-1

/bin/sh
0
0

230

Generated version 0.0.230 (no version tags found).
Using android versionCode 230
/usr/bin/docker build /home/runner/work/_actions/webbertakken/unity-builder/v2.0-aplha-5/action --file /home/runner/work/_actions/webbertakken/unity-builder/v2.0-aplha-5/action/Dockerfile --build-arg IMAGE=unityci/editor:2020.2.1f1-android-0 --tag unity-builder:2020.2.1f1-android-0
Sending build context to Docker daemon  3.091MB

Step 1/15 : ARG IMAGE
Step 2/15 : FROM $IMAGE
2020.2.1f1-android-0: Pulling from unityci/editor
171857c49d0f: Pulling fs layer
419640447d26: Pulling fs layer
61e52f862619: Pulling fs layer
54b0b6b2ac17: Pulling fs layer
9a4c76c6cf03: Pulling fs layer
283e0ad30484: Pulling fs layer
c67e0f7a2191: Pulling fs layer
cf5987363121: Pulling fs layer
0dc2ae63c061: Pulling fs layer
c3e57c00b537: Pulling fs layer
54b0b6b2ac17: Waiting
9a4c76c6cf03: Waiting
283e0ad30484: Waiting
c67e0f7a2191: Waiting
cf5987363121: Waiting
0dc2ae63c061: Waiting
c3e57c00b537: Waiting
61e52f862619: Download complete
419640447d26: Verifying Checksum
419640447d26: Download complete
171857c49d0f: Verifying Checksum
171857c49d0f: Download complete
9a4c76c6cf03: Verifying Checksum
9a4c76c6cf03: Download complete
283e0ad30484: Verifying Checksum
283e0ad30484: Download complete
c67e0f7a2191: Verifying Checksum
c67e0f7a2191: Download complete
0dc2ae63c061: Verifying Checksum
0dc2ae63c061: Download complete
c3e57c00b537: Verifying Checksum
c3e57c00b537: Download complete
54b0b6b2ac17: Verifying Checksum
54b0b6b2ac17: Download complete
171857c49d0f: Pull complete
419640447d26: Pull complete
61e52f862619: Pull complete
54b0b6b2ac17: Pull complete
9a4c76c6cf03: Pull complete
283e0ad30484: Pull complete
c67e0f7a2191: Pull complete
cf5987363121: Verifying Checksum
cf5987363121: Download complete
failed to register layer: Error processing tar file(exit status 1): write /opt/unity/Editor/Data/Tools/libembree.so.2: no space left on device
Error: The process '/usr/bin/docker' failed with exit code 1

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:7 (3 by maintainers)

github_iconTop GitHub Comments

3reactions
matrix3dcommented, Jan 19, 2021

https://github.com/matrix3d/buildu3d/blob/main/.github/workflows/android.yml

it is work

- name: Free Disk Space for Android
        run: |
          sudo swapoff -a
          sudo rm -f /swapfile
          sudo apt clean
          docker rmi $(docker image ls -aq)
          df -h
3reactions
davidmfinolcommented, Jan 11, 2021

Running out of disk space is a fairly common issue with Android builds (maybe we should add it https://game.ci/docs/troubleshooting/common-issues).

I use a script like this to free up some additional space on my Android builds:

      - name: Free Disk Space for Android
        run: |
          sudo swapoff -a
          sudo rm -f /swapfile
          sudo apt clean
          docker rmi $(docker image ls -aq)
          df -h
      - name: Build Unity Project
        uses: game-ci/unity-builder@v2.0-aplha-5
        ...

If freeing disk space like this doesn’t work for you, you may need to try using a self-hosted runner that has more disk space.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Top 3 Ways to Fix “No Space Left on Device” Error in Linux
Fix 1: Restart Processes Using Deleted Files. The most probable cause of the “No space left on device” error is a process still...
Read more >
How to Fix the "No Space Left on Device" Error on Linux
No Space on Device Possible Causes · Deleted File Reserved by Process · Not Enough Inodes · Bad Blocks.
Read more >
No space left on device - linux - Stack Overflow
Such difference between the output of du -sh and df -h may happen if some large file has been deleted, but is still...
Read more >
Knowledge Base:No space left on device while there is plenty ...
The first one is the most obvious: there must be space available on the file system, meaning that there are still unused data...
Read more >
How to Fix “No Space Left on Device” Error on Linux
Be Certain of the Space Left on the Device · Solution 1: Processes Using Deleted Files · Solution 2: Not Enough Inodes in...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found