매우 유용한 정보 감사합니다.
cleanup을 시도하기 전에, 복원(restore)을 수행하지 않고 백업 무결성을 확인할 수 있는 방법이 Discourse에 있을까요?
du -hx / | sort -h | tail -49의 결과입니다 (결과를 해석하기 쉬우므로 -h 옵션을 사용했습니다):
833M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/42/fs/var/www/discourse/vendor/bundle/ruby
833M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/42/fs/var/www/discourse/vendor/bundle/ruby/3.4.0
837M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/283/fs/var
837M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/283/fs/var/www
837M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/283/fs/var/www/discourse
837M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/283/fs/var/www/discourse/vendor
837M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/283/fs/var/www/discourse/vendor/bundle
837M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/283/fs/var/www/discourse/vendor/bundle/ruby
837M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/283/fs/var/www/discourse/vendor/bundle/ruby/3.4.0
839M /var/discourse/shared
839M /var/discourse/shared/standalone
840M /var/discourse
863M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/42
863M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/42/fs
868M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/283
868M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/283/fs
874M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/284
874M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/284/fs
874M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/43
874M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/43/fs
908M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/263/fs/usr
925M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/22/fs/usr
944M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/263
944M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/263/fs
961M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/22
961M /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/22/fs
1.3G /usr
1.4G /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/251
1.4G /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/251/fs
1.4G /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/251/fs/var
1.4G /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/251/fs/var/www
1.4G /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/251/fs/var/www/discourse
1.5G /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/227/fs/var
1.5G /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/227/fs/var/www
1.5G /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/227/fs/var/www/discourse
1.6G /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/227
1.6G /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/227/fs
2.5G /var/log
2.5G /var/log/journal
2.5G /var/log/journal/1d9299c9656046d6bd0e18d4a09c183c
2.7G /var/lib/containerd/io.containerd.content.v1.content
2.7G /var/lib/containerd/io.containerd.content.v1.content/blobs
2.7G /var/lib/containerd/io.containerd.content.v1.content/blobs/sha256
9.8G /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs
9.8G /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots
13G /var/lib
13G /var/lib/containerd
17G /var
20G /
docker volume ls -qf dangling=true의 출력은 비어 있었습니다. 실제로 docker volume ls도 비어 있습니다.
docker images -a:
IMAGE ID DISK USAGE CONTENT SIZE EXTRA
discourse/base:2.0.20260209-1300 50d2dae489a9 4.77GB 1.12GB
discourse/base:2.0.20260521-0047 27373b823bbe 4.89GB 1.17GB
local_discourse/app:latest 01527763be8d 6.9GB 1.63GB U
Docker에 대해 아는 것이 적어 이 출력을 진단하기 어렵지만, 로그만이라면 /var/log/가 다소 크고, 포럼을 하나만 운영하고 있는데 이미지가 3개 있는 것은 흥미롭습니다(아마도 이는 완전히 정상적인 상황일 수도 있겠지만요).
저장 공간에 대해 더 신경 써야 한다는 지적에 감사드립니다. 확장을 진행할 가능성이 높지만, 그렇게 하기 전에 좋은 학습 경험이 될 것 같습니다.