Skip to content

External volume should not be Isolated #1853

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

Open
as247 opened this issue May 8, 2025 · 0 comments
Open

External volume should not be Isolated #1853

as247 opened this issue May 8, 2025 · 0 comments

Comments

@as247
Copy link

as247 commented May 8, 2025

To Reproduce

  1. Create application with external volume, eg my_wp_data
volumes:
  my_wp_data:
    external: true
  1. Click Preview Compose
  2. External volume name got isolated, name changed to my_wp_data-wp-wordpress-foqxwk
volumes:
  my_wp_data-wp-wordpress-foqxwk:
    external: true

Current vs. Expected behavior

Current: volume which flagged as external got isolated by adding a suffix

volumes:
  my_wp_data-wp-wordpress-foqxwk:
    external: true

Expected that external volume should not be isolated with suffix

volumes:
  my_wp_data:
    external: true

Provide environment information

Os: Ubuntu 24.04 - arm64
Dokploy version: v0.22.3

Which area(s) are affected? (Select all that apply)

Docker Compose

Are you deploying the applications where Dokploy is installed or on a remote server?

Same server where Dokploy is installed

Additional context

No response

Will you send a PR to fix it?

No

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

No branches or pull requests

1 participant