Why is the capacity of containers increasing? about docker-rippled HOT 2 CLOSED

That's because the rippled process also reports logs to stdout, so you should also clean the docker container stdout logs ;)

To delete the logs on a Docker for Linux install, you can run the following for a single container:

echo "" > $(docker inspect --format='{{.LogPath}}' <container_name_or_id>)

Note that this requires root, and I do not recommend this. You could potentially corrupt the logfile if you null the file in the middle of docker writing a log to the same file. Instead you should configure docker to rotate the logs.

Lastly, you can configure docker to automatically rotate logs with the following in an /etc/docker/daemon.json file:

{
  "log-driver": "json-file",
  "log-opts": {"max-size": "10m", "max-file": "3"}
}

That allows docker to keep up to 3 log files per container, with each file limited to 10 megs (so a limit between 20 and 30 megs of logs per container). You will need to run a systemctl reload docker to apply those changes. And these changes are the defaults for any newly created container, they do not apply to already created containers. You will need to remove and recreate any existing containers to have these settings apply.

from docker-rippled.

For reference, if you delete the Ripple container,
/dev/mapper/centos-root 50G 8.1G 42G 17% /
As shown above, we were able to confirm that the capacity was reduced.

from docker-rippled.