@docker folder remains on old volume after successful move

[andrew-potachits]

I moved the container manager application from /volume1 to /volume3, but I see /volume1/@docker folder remaining and occupies 28Gb (btrfs subfolder). Can I safely remove this /volume1/@docker folder?

[007revad]

You should be able to safely remove the /volume1/@docker folder.

But if you want to make sure Container Manager is using the /volume2/@docker folder I would:

1. Stop Container Manager.
2. Rename /volume1/@docker to something else.
3. Reboot.
4. Start Container Manager and check all your containers are working as they should.
5. Then delete /volume1/@docker

There may also be a /volume1/@docker.bak that can you delete.

[bt-modbox]

I don't see a /volume1/@docker folder but there is a /volume1/@docker_backup which appears to contain a large amount of btrfs snapshots.. I presume I can safely remove it. The volume size started to increase while I was moving the Container Manager and later it's share. The weird part is that synology is reporting 933 GB of data (the largest folder according to CLI is @docker_backup 133.4 GB) on the volume after everything has been migrated to a new volume (apps and shares) but storage manager still says theres some "share" data on the volume which it cant really identify.

[bt-modbox]

I've proceeded to reboot the nas and it seems to have forced a clean up .. storage is being freed up.