Docker installation using bind volume

Ignition
,
1

Hello, I'm using docker to run a ignition gateway Edge on it, version 8.1.45. Everything looks great and the system is running well, however, the docker container is growing up very fast and it looks that the problem is coming from the /var/lib/docker/overlay2/ folder.
Maybe the problem is the way that I using to map the volume, I'm following the official documentation using named volume but I think that using bind volume could be better? at the end, I would like to have some control inside the volume in order to delete some big files as needed?
Thanking you in advance

Kind regards,
MF

2

Sounds like you're worried about disk space based on your post in this thread. Using a named volume versus a bind mount won't really change much for you here since you're referring to the storage layers of the container, not the volume. I'll let the other disk-space related discussion continue over in that other thread.