github-starred/templates
2
0
Fork 1
mirror of https://github.com/Dokploy/templates.git synced 2026-07-15 23:02:03 -05:00
Code Issues 2.9k Packages Projects Releases Wiki Activity

[GH-ISSUE #852] Templates should have the ability to opt-out from isolated deployments #15523

New Issue
Closed
opened 2026-07-14 22:45:37 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-07-14 22:45:37 -05:00
Owner
Copy Link

Originally created by @nktnet1 on GitHub (May 8, 2026).
Original GitHub issue: https://github.com/Dokploy/templates/issues/852

Template Name

Cloudflared

Relevant Logs of the Error

service cloudflared declares mutually exclusive network_mode and networks: invalid compose project

Steps to Reproduce the Error

  1. Create a service from the cloudflared template
  2. Update your CLOUDFLARE_TUNNEL_TOKEN (you can use any non-empty string to observe the bug)
  3. Deploy and observe the error

When does this error occur?

During template deployment

Additional Context

Workaround is to simply disable isolated deployments.

Solutions could either be to:

  1. Detect network_mode: host in the template and disable isolated deployment automatically
  2. Add a method to configure the template with isolated deployment off

As an aside, I see this in the Plunk template:

However, it does not do anything (isolated deployment is still enabled in settings).

Will you send a PR to fix it?

No

Originally created by @nktnet1 on GitHub (May 8, 2026). Original GitHub issue: https://github.com/Dokploy/templates/issues/852 ### Template Name Cloudflared ### Relevant Logs of the Error > service cloudflared declares mutually exclusive `network_mode` and `networks`: invalid compose project ### Steps to Reproduce the Error 1. Create a service from the cloudflared template 2. Update your `CLOUDFLARE_TUNNEL_TOKEN` (you can use any non-empty string to observe the bug) 3. Deploy and observe the error ### When does this error occur? During template deployment ### Additional Context Workaround is to simply disable isolated deployments. Solutions could either be to: 1. Detect `network_mode: host` in the template and disable isolated deployment automatically 2. Add a method to configure the template with isolated deployment off As an aside, I see this in the Plunk template: - https://github.com/Dokploy/templates/blob/d157cef3c357550aff801c336b99611813b522ae/blueprints/plunk/template.toml#L6-L7 However, it does not do anything (isolated deployment is still enabled in settings). ### Will you send a PR to fix it? No
GiteaMirror added the bug label 2026-07-14 22:45:37 -05:00
GiteaMirror commented 2026-07-14 22:45:39 -05:00
Author
Owner
Copy Link

@Siumauricio commented on GitHub (Jul 14, 2026):

This was addressed: the cloudflared template opts out of isolated deployment since ff465cd (#856), and Dokploy core now exposes an isolated-deployment toggle per compose service, so templates/users can opt out when needed.

<!-- gh-comment-id:4971725429 --> @Siumauricio commented on GitHub (Jul 14, 2026): This was addressed: the cloudflared template opts out of isolated deployment since ff465cd (#856), and Dokploy core now exposes an isolated-deployment toggle per compose service, so templates/users can opt out when needed.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
pull-request
Mirrored from GitHub Pull Request
 template
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/templates#15523
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?