Skip to content

fix: dedupe volume mount targets during recreate#765

Open
itsDNNS wants to merge 1 commit intoFinsys:mainfrom
itsDNNS:fix/recreate-volume-bind-dedupe
Open

fix: dedupe volume mount targets during recreate#765
itsDNNS wants to merge 1 commit intoFinsys:mainfrom
itsDNNS:fix/recreate-volume-bind-dedupe

Conversation

@itsDNNS
Copy link
Contributor

@itsDNNS itsDNNS commented Mar 15, 2026

Proposed change

This fixes a duplicate mount target during recreate/self-update on setups where Docker reports named volumes in HostConfig.Mounts instead of HostConfig.Binds. In that case Dockhand was only checking Binds, then adding the same destination again from inspectData.Mounts, which leads to errors like Duplicate mount point: /data.

The patch reuses one dedupe helper in both recreate paths and adds a small regression test covering the existing-target and missing-target cases.

Tested with:
npx tsx --test src/lib/server/mount-dedupe.test.ts

Closes #764

Type of change

  • Bug fix: non-breaking change which fixes an issue.
  • New feature / Enhancement: non-breaking change which adds functionality.
  • Breaking change: fix or feature that would cause existing functionality to not work as expected.
  • Other. Please explain:

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

Successfully merging this pull request may close these issues.

[BUG] v1.0.21getting update failed - Duplicate mount point: /database

1 participant