Skip to content

[Bug]: /api/v1/deploy?force=false forces a rebuild #8104

@n-e

Description

@n-e

Error Message and Logs

When I call the deploy API with force=false, my deployment is still force deployed, here's an excerpt of the logs :

2026-Jan-31 05:27:51.281468
[CMD]: docker exec h4c0ko0g0go0oo840o0kkccs bash -c 'cat /artifacts/build.sh'
2026-Jan-31 05:27:51.281468
cd /artifacts/XXX && set -a && source /artifacts/build-time.env && set +a && docker build --no-cache  --add-host coolify:10.0.1.4 --add-host coolify-db:10.0.1.6 --add-host coolify-realtime:10.0.1.7 --add-host coolify-redis:10.0.1.5 --add-host XXX:10.0.1.2 --network host -f /artifacts/XXX/Dockerfile --build-arg COOLIFY_URL --build-arg COOLIFY_FQDN --build-arg COOLIFY_BRANCH --build-arg COOLIFY_RESOURCE_UUID --build-arg COOLIFY_BUILD_SECRETS_HASH=XXX --build-arg 'COOLIFY_URL' --build-arg 'COOLIFY_FQDN' --build-arg 'COOLIFY_BRANCH' --build-arg 'COOLIFY_RESOURCE_UUID' --progress plain -t XXX:XXX /artifacts/XXX

Note that docker build is called with a no-cache argument

Steps to Reproduce

  1. Run curl 'https://XXX/api/v1/deploy?force=false&uuid=XXX' -H 'Authorization: Bearer XXX'
  2. Check that the deployment is force-rebuild
  3. Run curl 'https://XXX/api/v1/deploy?uuid=XXX' -H 'Authorization: Bearer XXX' without changing anything else
  4. Now the deployment isn't force rebuilt

Example Repository URL

No response

Coolify Version

v4.0.0-beta.462

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Ubuntu 24.04.3 LTS

Additional Information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    🔍 TriageIssues that need assessment and prioritization.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions