### TEARDOWN LAYER 1 — the machine: remove the throwaway nextcloud stack this spike created
2026-09-01T19:14:36Z
{"ok":false,"error":"stack \"nextcloud\" is still running — stop it first before removing"}

HTTP=409
### verify gone
nextcloud nextcloud:32.0.9-apache Up About a minute (healthy)
nextcloud-db mariadb:11.6 Up 15 minutes (healthy)
nextcloud-redis redis:7-alpine Up 15 minutes (healthy)
(empty above = containers gone)
nextcloud_nextcloud_db_data
nextcloud_nextcloud_html
nextcloud_nextcloud_redis_data
(empty above = volumes gone)
app.yaml
docker-compose.yml
nextcloud
paperless
romm
### stop first, then remove
{"ok":true,"message":"Stack nextcloud stop completed"}

HTTP=200
{"ok":true,"data":{"removed":"nextcloud","volumes_removed":null,"hdd_paths_removed":null,"hdd_paths_preserved":null},"message":"Stack nextcloud removed"}

HTTP=200
### verify gone
containers:
volumes:
hdd appdata:
nextcloud
paperless
romm
stack dir:
docker-compose.yml
### removing the spike's own leftover (128 MB the product did not remove)
2026-09-01T19:17:28Z
128M	/mnt/felhom-drives/hdd_1/appdata/nextcloud/
after:
paperless
romm
any nextcloud left anywhere under /mnt:
stack dir (template only, app.yaml gone = not deployed):
docker-compose.yml
images:
nextcloud:34.0.1-apache
nextcloud:32.0.9-apache
nextcloud:31.0.14-apache
### remove ONLY the three nextcloud images this spike pulled (targeted rmi, never a prune)
/dev/mapper/pve-vm--9201--disk--0   32G  958M   29G   4% /
removed nextcloud:31.0.14-apache
removed nextcloud:32.0.9-apache
removed nextcloud:34.0.1-apache
remaining nextcloud images:
(none)
/dev/mapper/pve-vm--9201--disk--0   32G  958M   29G   4% /
stack dir now:
.
..
.felhom.yml
docker-compose.yml
