Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

File space #54

Open
foxhoundv opened this issue Mar 3, 2021 · 1 comment
Open

File space #54

foxhoundv opened this issue Mar 3, 2021 · 1 comment

Comments

@foxhoundv
Copy link
Contributor

I use this Docker Install which is pretty basic, it just allows for nginx use and OnlyOffice. I prefer OnlyOffice vs Collabora, and not really wanting to change that. Anyways. It all installs fine and works. So I migrated my data from a previous Nextcloud install and even though I have 800Gb for my Docker machine, and I migrated 56Gb from my old machine, It says I am running out of space. So after doing some research I did “df -h --total” in my command line and it shows me:

overlay 98G 90G 3.3G 97% /var/lib/docker/overlay2/215ae8c0afd1def91650ffdb7a80cea6a69a020969088bb806a047629d38d401/merged overlay 98G 90G 3.3G 97% /var/lib/docker/overlay2/8e92d5e848172d9bc64ca30081e3871a8208ffa01ba7c70b0968abe339caa459/merged overlay 98G 90G 3.3G 97% /var/lib/docker/overlay2/3fe9dca5cf8843c8b518fe1e896fd4fb28b0c625829e6a6123bed0f260ad952e/merged overlay 98G 90G 3.3G 97% /var/lib/docker/overlay2/f686eca43dd4abd6f63d43d335ac13f900c9cd434b1a143bcc0e5e7092b52532/merged

When I close the containers these disappear. I know that the image has 3 stacked containers. One for the OnlyOffice, one for NGINX, and one for Nextcloud. I have my data volume for Nextcloud binded to a folder on the host machine but I still get this issue. I don't know if this is an issue with using these stacked or if it is a Nextcloud/Docker image problem.

@localjo
Copy link

localjo commented Apr 18, 2021

I've also noticed some issues with unexpectedly high disk space usage on a fresh install. I haven't completely determined the root cause yet, but I was able to reclaim some space by running docker volume prune while all of the docker containers are running, to prune unused volumes that somehow got created. My disk usage is still higher than expected, but I wonder if you've tried this, and if it helps?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants