Skip to content
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

Open
juandl opened this issue Dec 12, 2024 · 10 comments
Open

Volumes Only show "File" as type #866

juandl opened this issue Dec 12, 2024 · 10 comments

Comments

@juandl
Copy link

juandl commented Dec 12, 2024

To Reproduce

I have a docker-compose (raw) and i tried to add a new Volume but is only show "File" as a type

image

Current vs. Expected behavior

Allow to mount file/dir volumen

Provide environment information

Dokploy: v0.14.1 (Self hosted)
Ubunutu 22

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

@juandl juandl added the bug Something isn't working label Dec 12, 2024
@ohblue
Copy link

ohblue commented Dec 13, 2024

i have the same issue.

@Siumauricio
Copy link
Contributor

Please add a minimal reproducible

@Siumauricio Siumauricio added question Further information is requested awaiting-response and removed bug Something isn't working question Further information is requested labels Dec 14, 2024
@juandl
Copy link
Author

juandl commented Dec 15, 2024

@Siumauricio

-Install dokploy using script.
-Create an app for docker compose
-Add docker compose using RAW
-Go to settings -> Volume
-Shows only "File"

@LickABrick
Copy link

I have had the same thing from the start (always thought this was not implemented yet). Last week I noticed however that if I add a volume to a database instance I do have multiple options.

Compose (mine is from a git repo):
image

Database:
image

@FaintGhost
Copy link

i have the same issue.

@channchetra
Copy link

I have the same problem here.

@Siumauricio
Copy link
Contributor

I still don't understand the problem, can anyone give a way to reproduce the problem? and to understand what is wrong?

@channchetra
Copy link

channchetra commented Dec 19, 2024

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

@Siumauricio
Copy link
Contributor

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

@channchetra
Copy link

Yes after I try to rearrange my compose it seems this is fine 🙏

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

6 participants