I am a bit confused. OneDev creates cache inside /opt/onedev/site/cache. If you mounted /opt/onedev to a different volume, the cache folder should also resides on that volume. I tested at my side and it works this way.

And yet, while an image was being built, I noticed the space on the boot volume decreased rapidly. I have checked the mounting point of /opt/onedev and it is indeed on another partition than the boot volume.

Here is the docker-compose.yml file I am using:

version: "3"

services:
  onedev:
    image: 1dev/server
    container_name: odv
    restart: unless-stopped
    ports:
      - 6610:6610
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /mnt/nvm204/odv/dta:/opt/onedev

And the space on nvm204 stayed almost identical.

I think I have found the culprit: I was using DOCKER_BUILDKIT=1 in my build instructions and it was caching on the main disk. Sorry for the waste of time.

Thanks for letting me know.

No, in fact please reopen it: I am testing it with another build with BUILDKIT inactivated and the space on boot disk is still shrinking (not at the same pace than before but still). Don't you think docker is the culprit, writing stuff in its image cache? Also remember: I am using the Server Shell job executor.

If docker writes stuff to boot volume, it is out of OneDev's control. It is not an issue of OneDev's cache. You may need to figure out which folder docker is written its temp file and then mount that folder to a different volume directly on the host machine (since OneDev docker operation is relayed to host machine).

OK, you are right. But this was in case it happens to somebody else.