[narcisonunez]

What is this PR about?

Two bugs when creating a file mount:

• Without filePath (possible via the API), the content was written over the service's whole files/ directory. It's now rejected.
• If the stack was deployed before the mount existed, Docker had already created the path as an empty directory, so writing the file failed (EISDIR) while the mount was still saved. The stale directory is now replaced, as updateFileMount already does.

Checklist

• You created a dedicated branch based on the canary branch.
• You have read the suggestions in the CONTRIBUTING.md file https://github.com/Dokploy/dokploy/blob/canary/CONTRIBUTING.md#pull-request
• You have tested this PR in your local instance.

Issues related (if applicable)

closes #5292

Confidence Score: 5/5

This PR appears safe to merge; no new actionable issues were found.

Summary

This PR rejects missing or unsafe file paths and replaces empty directories Docker created with files.

• File mounts stay within the service’s files folder.
• File mounts replace Docker’s empty placeholder with the configured file.

_{Reviews (3) · Last reviewed commit: "fix(mounts): validate file paths on upda..." · Reviewed by Greptile}