Dokploy / Dokploy/dokploy

Add Custom Pipeline Steps for Docker Compose Builds

Open
#2,371 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
37.4k
Forks
3k
Avg merge
1d 3h
Merged PRs (30d)
73

Description

What problem will this feature address?

Hi Dokploy Team,

I’d like to request the ability to define custom pipeline steps for Docker Compose builds, instead of running the build process as a single fixed command.

Reason:
Currently, the Docker Compose build step is executed as a single docker compose build (or similar) command, which limits flexibility. In some cases:
• Connecting containers to custom networks
• Copying environment files before build
• Mounting temporary build volumes
• Running pre-build scripts (e.g., npm install, yarn install, database migrations)

This would make it possible to perform complex build preparations and post-build tasks without bypassing Dokploy’s pipeline system.

Thank you for considering this feature — it would make Dokploy more adaptable for advanced Docker deployments.

Describe the solution you'd like

Update the current pipeline not to start "docker" and add more build steps

Describe alternatives you've considered

i have no idea

Additional context

No response

Will you send a PR to implement it?

Yes

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the pipeline entry point that currently invokes the Docker Compose build command and read how pipeline steps are represented and executed. Define the expected behavior for custom pre-build, build, and post-build steps, including ordering and environment handling. Done means the pipeline supports the requested step sequence with tests covering a representative Compose build.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose
Domain
build-system, devops, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.