You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
sv stop docker ; cd /var/lib/docker; rm -rf * ; cd ; sv start docker
docker-compose build; docker-compose up -d
-bash-5.2# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
stunnel latest 0554e3d1cee5 9 minutes ago 283MB
inspi4 latest 1ede30fc0a32 14 minutes ago 777MB
-bash-5.2#
2.1G total
-bash-5.2# pwd
/var/lib/docker
-bash-5.2# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/vda1 9.8G 7.1G 2.3G 77% /
.....
overlay 9.8G 7.1G 2.3G 77% /var/lib/docker/overlay2/75739496355a924966400aeb7310a399938cd2557572dabdc8f4ed91b1aaa657/merged
overlay 9.8G 7.1G 2.3G 77% /var/lib/docker/overlay2/a46171e0843c13e02a546d054062a1e648c0dbe03cdbd5894f10ea04c01c1c2a/merged
-bash-5.2#
Bought some time..
My experience Ive had better luck with btrfs .. ZFS is probably fine too I have had issues with overlay though where docker rmi didn't free up disk space as I expected but then again I don't run into this problem often in general
The text was updated successfully, but these errors were encountered:
Typically you want to use btrfs for docker, but this will ahve to do:
/var/cache/xbps
is a space hogdocker ps -aq | xargs -i docker stop {} ; docker ps -aq | xargs -i docker rm {}
sv stop docker ; cd /var/lib/docker; rm -rf * ; cd ; sv start docker
docker-compose build; docker-compose up -d
Bought some time..
My experience Ive had better luck with btrfs .. ZFS is probably fine too I have had issues with overlay though where
docker rmi
didn't free up disk space as I expected but then again I don't run into this problem often in generalThe text was updated successfully, but these errors were encountered: