The 5 GB Ghost in the Nextcloud Container: How an Orphaned Euro-Office Filled My Boot Disk

Nextcloud AIO reported “Low on space”. An automatically started Euro-Office container occupied almost 5 GB on my boot disk, even though I had selected no office suite.
How I noticed
Nextcloud is my central storage; all of my documents live there. When a storage warning appeared one morning, I wanted to know which disk was affected:
nc.phoenix.cloud: Low on space!
The drive that hosts the mastercontainer volume has less than 5 GB free space. Container updates and backups might not succeed due to that!
Less than 5 GB free – even though my data was supposed to live on a separate disk. And the message was not an isolated event: for a few days, the system had also been reporting “Daily backup failed”. Time to get to the bottom of it.
The diagnosis: A Docker stack on a disk that is too small
The separate data disk still had plenty of room: the data directory (/mnt/ncdata) lives on a dedicated 196 GB disk (/mnt/nc_storage) that was only about 6 % full. Space was running low on the boot disk’s root filesystem:
/dev/sda3 20G 14G 4,8G 75% /
The root filesystem was around 20 GB in size and 75 % full. The virtual boot disk itself was 25 GB. When looking for large directories, Docker stood out:
/var/lib/docker 17G
overlay2 (images) ~15G
volumes ~1,9G
These directory sizes cannot be directly reconciled with df: Docker layers and their mounts need to be considered separately. Among the images, one item stood out:
ghcr.io/nextcloud-releases/aio-eurooffice:latest 4.43GB

Euro-Office. I had deliberately set up my instance without an office suite. Yet the container had been running unnoticed for three months. Its image occupied 4.43 GB; together with the writable container layer, the total was around 5 GB. The associated volume, however, was empty (0 B). The container served no purpose in my setup.
The orphaned container. In my case, the intended AIO configuration and the Docker containers actually running did not match. That is why I checked both: deselecting an office suite does not mean its container, image, and volume have also been removed.
How it happened: A known auto-update bug
At first I wondered whether I had accidentally changed the office selection. Research then led me to a known Nextcloud AIO bug. GitHub issue #8416 describes exactly this situation:
Auto-Update to 13.3.1 enables EuroOffice if Nextcloud was configured to not start an office container
AIO stored the office selection as three separate boolean options. The choice “no office” was never persisted explicitly. The introduction of Euro-Office changed the implicit default. An automatic update could therefore start Euro-Office even though no office suite had deliberately been selected before. The situation addressed by the fix matched my installation.
The phenomenon “an auto-update installs Euro-Office” is also documented independently, for example in “Moving to Euro-Office – Part 1” on WirelessMoves: there it was even described as a pleasant surprise, because Euro-Office was wanted – in my case it was not.
The fix from PR #8441 was released with AIO v13.4.0 in July 2026. It accounts for all office suites having been disabled before Euro-Office was introduced. On my already affected installation, however, the leftovers were still there; I had to remove them separately.
The fix: Verify, clean up, check
1. Verify the AIO configuration
Before cleaning up, I compared the office selection with the AIO configuration. The application containers were stopped; the mastercontainer had to remain running for docker exec:
docker exec nextcloud-aio-mastercontainer \
grep -ioE '"(is[A-Za-z]+Enabled)": *(true|false)' \
/mnt/docker-aio-config/data/configuration.json
My configuration at the time included these flags:
"isClamavEnabled": true
"isOnlyofficeEnabled": false
"isCollaboraEnabled": false
There was no isEuroofficeEnabled flag yet; the OnlyOffice and Collabora options were disabled. This matched my intended configuration without an office suite. The missing flag alone would not be sufficient evidence, though. Deselecting the suite through the interface also does not replace removing the container, image, and volume.
2. Remove the container and its leftovers
Once I had checked the configuration and confirmed that the volume was empty, I removed the unwanted container and its leftovers:
docker stop nextcloud-aio-eurooffice
docker rm nextcloud-aio-eurooffice
docker image rm ghcr.io/nextcloud-releases/aio-eurooffice:latest
docker volume rm nextcloud_aio_eurooffice
Together with the container layer, that was almost 5 GB – matching the figure from nextcloud.com, which lists about 5 GB of disk space for the Euro-Office image.
3. Restart the AIO containers and check the app
After removal, I restarted the AIO containers through the interface – and checked whether the office connector app was still in the “Enabled” list in Nextcloud:
docker exec --user www-data nextcloud-aio-nextcloud php occ app:list | grep -i office
I still found office: 1.0.0 there. Since the filtered excerpt alone does not show whether the app is enabled, I also checked the full output of occ app:list. The app was listed under “Enabled” and pointed at the document server I had just removed. I disabled it:
docker exec --user www-data nextcloud-aio-nextcloud php occ app:disable office
Follow-up
After the next AIO update, a quick check whether the container reappears is worthwhile:
docker ps -a | grep eurooffice
If it reappears, I will check the AIO version and saved office selection again. An unexpected selection can be deselected and saved through the AIO interface. Its reappearance alone does not prove which setting is responsible.
Results and lessons
| before | after | |
|---|---|---|
Boot disk / usage | 14 GB (75 %) | 9 GB (49 %) |
Free on / | 4.8 GB | 9.6 GB |
| Euro-Office container | running (3 months) | removed |
The table shows the effect of the cleanup, before resizing the disk. I also expanded the virtual boot disk online from 25 GB to 50 GB: using qm resize on the Proxmox host, followed by growpart and resize2fs inside the VM. This provides more room for future updates. The “Low on space” warning is gone, and the daily backup runs without alarms again.
Three lessons from this story:
- Check running containers after updates. An automatic update can also change the actual installation. An occasional look at
docker ps -aanddf -his worth it. - Keep data and system separate. The separate data disk still had room even as the boot disk ran low. Updates and backups, however, also need enough free space on the system disk.
- Compare bug reports with releases. The issue and fix helped me understand the unexpected container. The release history is also worth a look.
Cleaning up reclaimed 4.8 GB. Since then, checking AIO has also meant looking at which containers are actually running.
Status: 8 November 2026. Sources: GitHub issue nextcloud/all-in-one#8416, fix PR #8441 (AIO v13.4.0), WirelessMoves and nextcloud.com. Images: AI-generated conceptual illustrations, not browser screenshots.