fix(dev): add Docker volume path mapping to testing-host for database deployments - #9534
Merged
Merged
Conversation
… deployments Database deployments generate bind mounts referencing the internal Docker volume path (/var/lib/docker/volumes/coolify_dev_coolify_data/_data) which doesn't exist in the testing-host container. This adds the missing volume mount so both /data/coolify and the Docker volume path resolve correctly. Fixes coollabsio#9533 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Member
|
Thank you for the PR! 💜 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
The testing-host container in
docker-compose.dev.ymlmountsdev_coolify_dataat/data/coolify, but when Coolify generates Docker Compose configs for standalone database deployments (PostgreSQL, MongoDB, etc.), it creates bind mounts referencing the internal Docker volume path (/var/lib/docker/volumes/coolify_dev_coolify_data/_data). Since that path doesn't exist in the testing-host container, database deployments fail with "bind source path does not exist."This adds a second volume mount mapping
dev_coolify_datato the Docker volume path so both paths resolve correctly in the dev environment.Issues
Category
AI Assistance
If AI was used:
Testing
spin upto start dev environmentdev_coolify_dataaccessible at both/data/coolifyand/var/lib/docker/volumes/coolify_dev_coolify_data/_datainside the testing-host containerContributor Agreement
Important