Inodes issue on docker

[Mandrake158]

So I recently moved from the native linux version to docker, as I changed everything to LXCs and dockers

The LXC was "full" even though it still had plenty space left, so when I check the inodes, I saw it was at 100% used. I deleted all the dockers and started managing each, one by one, to find the issue

When I left ASF running for a day, the inode usage went from 16% to 49%, and after deleting the image, it went back to 16%. I tried checking if anyone had issues with inodes, but searching inodes didn't result in anything

Here is the my compose config

compose.yml
asf:
image: justarchi/archisteamfarm:latest
container_name: asf
environment:
- PUID=0
- PGID=0
- TZ=Etc/UTC
volumes:
- /root/asf:/app/config
logging:
driver: none
ports:
- 1242:1242
restart: unless-stopped

Yes, its running as root as it is under unprivilidge LXC and didn't want to mess with permissions between containers and LXCs. And the /root/asf folder is under root:root, and there is no issue with the permissions as I can farm and log into the webUI

[JustArchi]

There is nothing special in ASF docker version that isn't happening with normal one. I don't know why you ran out of inodes, that's something LXC or docker-specific.

The only thing that comes to my mind is that perhaps ASF auto-update overwrote original files in result creating a need of new overlay on top of existing one, which is working according to the intended use case - you can try using :released tag and checking if it helps.

If not, then the only other place is log.txt that ASF writes, you can either mount that to root filesystem or disable with custom NLog.config and seeing if perhaps that fixes the issue.

/app/config is already mounted by you, so no issue there. If you're using custom plugins then you might need to ensure that they're also not writing some arbitrary dirs, with default ones everything, if any, is happening inside config dir.

In any case, I can only think of possible options, your issue is docker/lxc-specific, so support options are limited in this regard, especially because we consider docker to be advanced setup, and we warn in the wiki about new problems that will arise from using it with ASF.