-
-
Notifications
You must be signed in to change notification settings - Fork 553
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
Volumes Only show "File" as type #866
Comments
i have the same issue. |
Please add a minimal reproducible |
-Install dokploy using script. |
i have the same issue. |
I have the same problem here. |
I still don't understand the problem, can anyone give a way to reproduce the problem? and to understand what is wrong? |
There's a discrepancy in volume mounting options when creating services. In Compose and Template mode, only "File" mounts are available in the advanced settings. However, when creating applications or databases the expected "Bind" and "Volume" mount options are present. Recording.2024-12-19.132311.mp4 |
It is not a discrepancy, it is simply that it does not make sense to have bind mounts from the interface because in docker compose the volumes are handled through the compose file, we only offer the file mounts because it is the only thing that is needed to deploy any template and a proof of them is that we have complex templates like supabase https://github.com/Dokploy/dokploy/blob/canary/apps/dokploy/templates/supabase/index.ts |
Yes after I try to rearrange my compose it seems this is fine 🙏 |
To Reproduce
I have a docker-compose (raw) and i tried to add a new Volume but is only show "File" as a type
Current vs. Expected behavior
Allow to mount file/dir volumen
Provide environment information
Which area(s) are affected? (Select all that apply)
Application, 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
The text was updated successfully, but these errors were encountered: