No space left on device

[HariSekhon]

I've noticed this "No space left on device" error breaking various builds recently... I can't be sure but I think it seems to happen more around midnight GMT, perhaps because that is peak time US...

[caervs]

Hi @HariSekhon. Could you please contact support@docker.com with more info including links to particular builds?

[lalet]

Hi I am also getting the same issue. Is this something to do with the dockerhub or the image size ? These builds were successful a month back and we have not added anything new.

https://hub.docker.com/r/bigdatalabteam/hcp-prefreesurfer/builds/bxazzkztiodqrus7lqaj9hp/

[CM2Walki]

Hello,
since this issue already exists (even though it's old). I'm running into the "no space left on device" issue as well. I'm using Docker Hub automated builds to create game server images which are usually quiet large (~ 20GBs during build). I did have success in the past, but now it keeps failing again.

"Error processing tar file(exit status 1): write /home/steam/csgo-dedicated/platform/shaders/fxc/character_ps30.vcs: no space left on device"

Link to build:
https://cloud.docker.com/u/cm2network/repository/registry-1.docker.io/cm2network/csgo/builds/ac9f28d9-22bb-4194-9322-22c7e45bf5c9

Repository:
https://github.com/CM2Walki/CSGO
https://cloud.docker.com/u/cm2network/repository/docker/cm2network/csgo

Could it be that the workers have a hard limit of like 20 GBs per build? And if yes, is it possible to include larger image limits in paid plans?

[Anon-Exploiter]

Hello,
since this issue already exists (even though it's old). I'm running into the "no space left on device" issue as well. I'm using Docker Hub automated builds to create game server images which are usually quiet large (~ 20GBs during build). I did have success in the past, but now it keeps failing again.

"Error processing tar file(exit status 1): write /home/steam/csgo-dedicated/platform/shaders/fxc/character_ps30.vcs: no space left on device"

Link to build:
https://cloud.docker.com/u/cm2network/repository/registry-1.docker.io/cm2network/csgo/builds/ac9f28d9-22bb-4194-9322-22c7e45bf5c9

Repository:
https://github.com/CM2Walki/CSGO
https://cloud.docker.com/u/cm2network/repository/docker/cm2network/csgo

Could it be that the workers have a hard limit of like 20 GBs per build? And if yes, is it possible to include larger image limits in paid plans?

Kinda same, I'm creating a container for CS:GO as well. Ran into the following error:

URL: https://hub.docker.com/r/uexpl0it/csgo-server

Your comment is an year old, it seems it won't get fixed any time soon. Did you find a workaround except for building and uploading locally?

[CM2Walki]

Kind of a work around, I guess?

I went with downloading the entire dedicated server on first start of the container. Now it's not the best solution, but it had the added advantage of apparently doing something against image corruption. See CM2Walki/TF2#2.

You can check out my new image here: https://github.com/CM2Walki/CSGO

[Anon-Exploiter]

Wow, looking at the source, you're using CS:GO's image as the base. Was thinking of using your base but have setted mine to build a vanilla server without any mods too, if that doesn't work, will upload it manually and then use it further on for mods.

Thanks for the idea.

[github-actions]

We are clearing up our old issues and your ticket has been open for 6 months with no activity. Remove stale label or comment or this will be closed in 15 days.

[HariSekhon]

.

[casperfrx]

. indeed.

I am currently building an even downsizde version of Intel's OpenAPI package and it can't build it. Having at least the option, paid or not, to build larger images would be nice.

[github-actions]

We are clearing up our old issues and your ticket has been open for 6 months with no activity. Remove stale label or comment or this will be closed in 15 days.

[CM2Walki]

I think this is still relevant

[glenn-jocher]

We are using autobuild with the YOLOv5 repo https://github.com/ultralytics/yolov5 on a paid plan and keep getting this error message.
https://hub.docker.com/r/ultralytics/yolov5

[HariSekhon]

FYI I've found less problems using regular free CI/CD to build DockerHub images and since DockerHub stopped allowing free automated builds for open source projects I've settled on using the wonderful GitHub Actions instead.

I even published a GitHub Actions reusable workflow to do docker builds with automatic layer caching by committing a mere few lines of yaml to .github/workflows/docker_build.yaml in your GitHub repo:

on: [push]
jobs:
  docker_build:
    uses: HariSekhon/GitHub-Actions/.github/workflows/docker_build.yaml@master
    with:
      repo: user/repo  # your DockerHub user/repo
      tags: latest v1.1
    secrets:
      DOCKERHUB_USER: ${{ secrets.DOCKERHUB_USER }}
      DOCKERHUB_TOKEN: ${{ secrets.DOCKERHUB_TOKEN }}

My GitHub Actions library repo and more details can be found here:

https://github.com/harisekhon/github-actions#docker-build-and-push-to-dockerhub

It also starts and builds quicker than waiting for DockerHub in my experience.