Change data volume #75

New Issue

Open

opened 2026-03-18 01:44:45 +00:00 by jeppebundsgaard · 2 comments

jeppebundsgaard commented 2026-03-18 01:44:45 +00:00

Copy Link

My harddisk is full. I want to move the nextcloud datadir to a new disk, mounted at /mnt/HC1. I have tried a lot. The solution I would believe would work is this:

in ~/.abra/servers/domain.com/sky.domain.com.datadir.yml I have

volumes: sky_domain_com_nextdata: driver: local driver_opts: type: none device: /mnt/HC1/sky-domain-data o: bind

and in .env:
COMPOSE_FILE="compose.yml:../../servers/domain.com/sky.domain.com.datadir.yml"

the yml is used, but the volume is not changed to the new version.

I have tried to delete the volume on the server:
docker volume rm sky_domain_com_nextdata but I get:

Error response from daemon: remove sky_domain_com_nextdata: volume is in use - [1c2c5bf124cde8a8ff090c21bcb6853d498b873cdbe0736af48485489c7db184, 1dacc4a504c0647f24c86995387e1efe78944cde489cb915d5dc68a57bb97b81, 239c5348ffe52b6230de5dc85b3acbaadbcb31ab7ae0ca79cc343e07f82a373a]

What is the best way to migrate to another drive?

My harddisk is full. I want to move the nextcloud datadir to a new disk, mounted at /mnt/HC1. I have tried a lot. The solution I would believe would work is this: in `~/.abra/servers/domain.com/sky.domain.com.datadir.yml` I have ` volumes: sky_domain_com_nextdata: driver: local driver_opts: type: none device: /mnt/HC1/sky-domain-data o: bind ` and in .env: `COMPOSE_FILE="compose.yml:../../servers/domain.com/sky.domain.com.datadir.yml"` the yml is used, but the volume is not changed to the new version. I have tried to delete the volume on the server: `docker volume rm sky_domain_com_nextdata` but I get: > Error response from daemon: remove sky_domain_com_nextdata: volume is in use - [1c2c5bf124cde8a8ff090c21bcb6853d498b873cdbe0736af48485489c7db184, 1dacc4a504c0647f24c86995387e1efe78944cde489cb915d5dc68a57bb97b81, 239c5348ffe52b6230de5dc85b3acbaadbcb31ab7ae0ca79cc343e07f82a373a] What is the best way to migrate to another drive?

decentral1se commented 2026-03-18 08:32:44 +00:00

Owner

Copy Link

Hey @jeppebundsgaard! We should totally have more docs on this!

Error response from daemon: remove sky_domain_com_nextdata: volume is in use

That is usually because there is a container/stack still using the volume, you need to undeploy first.

@3wordchant I think you might have a good angle on this.

I myself would probably just undeploy everything, mv all the shit to my new drive and then symlink the volume path to the new drive? I'm a pretty shitty sysadmin tbh...

Hey @jeppebundsgaard! We should totally have more docs on this! > Error response from daemon: remove sky_domain_com_nextdata: volume is in use That is usually because there is a container/stack still using the volume, you need to undeploy first. @3wordchant I think you might have a good angle on this. I myself would probably just undeploy everything, `mv` all the shit to my new drive and then symlink the volume path to the new drive? I'm a pretty shitty sysadmin tbh...

jeppebundsgaard commented 2026-03-18 09:10:33 +00:00

Author

Copy Link

Hey @jeppebundsgaard! We should totally have more docs on this!

Would be much appreciated :-)

Error response from daemon: remove sky_domain_com_nextdata: volume is in use

That is usually because there is a container/stack still using the volume, you need to undeploy first.

I did undeploy, but the containers were still lying around as DEAD, and I couldn't remove them (the container-ids were non-existing).

I myself would probably just undeploy everything, mv all the shit to my new drive and then symlink the volume path to the new drive? I'm a pretty shitty sysadmin tbh...

At 3 AM, I ended up doing exactly that: Moving, symlinking. But I also felt that was not the most transparent and sustainable solution.

> Hey @jeppebundsgaard! We should totally have more docs on this! Would be much appreciated :-) > > Error response from daemon: remove sky_domain_com_nextdata: volume is in use > > That is usually because there is a container/stack still using the volume, you need to undeploy first. I did undeploy, but the containers were still lying around as DEAD, and I couldn't remove them (the container-ids were non-existing). > I myself would probably just undeploy everything, `mv` all the shit to my new drive and then symlink the volume path to the new drive? I'm a pretty shitty sysadmin tbh... At 3 AM, I ended up doing exactly that: Moving, symlinking. But I also felt that was not the most transparent and sustainable solution.

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

renovate/mariadb-12.x

renovate/docker.elastic.co-elasticsearch-elasticsearch-9.x

renovate/redis-8.x

renovate/mariadb-11.x

renovate/nginx-1.x

renovate/docker.elastic.co-elasticsearch-elasticsearch-8.x

renovate/nextcloud-32.x

renovate/ghcr.io-nextcloud-releases-whiteboard-1.x

feature/imaginary

kc_stable

nextcloud-v28

add-theming-v28.0.5

add-theming

update-nginx-conf

split-bbb-onlyoffice-compos

split-onlyoffice-bbb-config

authentik_sso

healthchecks

occ_cmds

auto_app_install

embed_nextcloud_in_iframe

auto_configure_sso

add-postgres-db

13.0.1+32.0.3-fpm

13.0.0+32.0.3-fpm

12.1.0+31.0.6-fpm

12.0.1+31.0.6-fpm

12.0.0+31.0.6-fpm

11.4.0+30.0.6-fpm

11.4.0+30.0.10-fpm

11.3.0+30.0.6-fpm

11.2.0+30.0.6-fpm

11.1.0+30.0.6-fpm

11.0.1+30.0.4-fpm

11.0.0+30.0.4-fpm

10.0.0+30.0.4-fpm

9.2.0+29.0.8-fpm

6.0.11+28.0.10-fpm

6.0.10+28.0.10-fpm

6.0.9+28.0.10-fpm

9.1.2+29.0.5-fpm

6.0.8+28.0.5-fpm

6.0.7+28.0.5-fpm

9.1.0+29.0.5-fpm

9.0.0+29.0.5-fpm

6.0.6+28.0.5-fpm

8.0.1+29.0.3-fpm

8.0.0+29.0.1-fpm

7.0.3+29.0.1-fpm

6.0.5+28.0.5-fpm

7.0.2+29.0.1-fpm

7.0.1+29.0.1-fpm

7.0.0+29.0.0-fpm

6.0.4+28.0.5-fpm

6.0.3+28.0.5-fpm

6.0.2+28.0.5-fpm

5.0.3+27.0.1-fpm

6.0.1+28.0.2-fpm

6.0.0+28.0.1-fpm

5.2.0+27.1.5-fpm

5.1.1+27.1.5-fpm

5.1.0+27.1.3-fpm

5.0.2+27.0.1-fpm

5.0.1+27.0.1-fpm

5.0.0+27.0.0-fpm

4.0.7+26.0.2-fpm

4.0.6+26.0.2-fpm

4.0.5+26.0.2-fpm

4.0.4+26.0.2-fpm

4.0.3+26.0.2-fpm

4.0.2+26.0.2-fpm

4.0.1+26.0.1-fpm

4.0.0+26.0.1-fpm

3.3.2+25.0.6-fpm

3.3.1+25.0.5-fpm

3.3.0+25.0.5-fpm

3.2.0+25.0.4-fpm

3.1.2+25.0.4-fpm

3.1.1+25.0.1-fpm

3.1.0+25.0.1-fpm

3.0.1+25.0.1-fpm

3.0.0+25.0.1-fpm

2.1.4+24.0.6-fpm

2.1.3+24.0.5-fpm

2.1.2+24.0.3-fpm

2.1.1+24.0.2-fpm

2.1.0+24.0.0-fpm

2.0.0+23.0.4-fpm

1.0.0+23.0.1-fpm

Labels

Clear labels

bug

Something is not working

documentation

For issues that are calling out documentation gap

duplicate

This issue or pull request already exists

enhancement

New feature

help wanted

Need some help

invalid

Something is wrong

question

More information is needed

wontfix

This won't be fixed

No Label

Milestone

No items

No Milestone

Assignees

Clear assignees

3wordchant aadil abra-bot ammaratef45 Apfelwurm appletalk arjan basebuilder Brooke carla cas codegod100 coopcloud cyrnel decentral1se devydave fauno flancian Frando iexos jade javielico jjsfunhouse jmakdah2 joe-irving kawaiipunk knoflook kolaente lambdabundesverband linnealovespie marlon mayel mirsal moosemower moritz nicksellen notplants p4u1 pau pharaohgraphy PhiNatalie renovate-bot ripclap rix rscmbbng sef simon sixsmith stevensting tobias trav val vaznasty virtualboys wolcen wykwit xynosis yksflip

No Assignees

2 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/nextcloud#75

No description provided.