how to handle docker-compose port conflict (e.g., port 3000) in dokploy git deploy without forking
hello dokploy community,
i'm deploying rowboat (https://github.com/rowboat/rowboat) using dokploy's 'git' provider (repo url + docker-compose.yml path), needed because the compose file uses build:. required env vars are set in the ui.
deploy clones & builds images fine, but fails starting the main rowboat container with this error:
the issue is the source docker-compose.yml maps ports: - "3000:3000", conflicting with host port 3000 (likely used by dokploy itself).
using the 'git repo + compose path' method, i don't see how to override/change the ports: section before docker compose up.
i need to avoid forking the original repository just to change this, mainly due to the hassle of keeping it updated. changing dokploy's port also seems complex/undesirable.
has anyone faced this specific host port conflict with git deploys in dokploy?
is there a dokploy-specific way (like a compose override mechanism, using env vars to control ports without changing the file, or another method) to handle this without forking the source repo?
any tips appreciated! thanks!
2 Replies
there's no way to update the compose file without modifying manually
tks, so does that mean I would have to fork it?
do you know if another tool, like Coolify, allows this? I'm enjoying dokploy for other applications, but I don't know how to solve this issue.