Railpack install fails: curl --retry-all-errors not supported (exit code 2)

[StruggleYang]

To Reproduce

1. Install Dokploy on a fresh server (Rocky Linux 8).
2. Create a new application using a Railpack-based build.
3. Start the deployment.
4. Observe the build logs during the “Installing railpack” step.
5. The build fails immediately with a curl error before railpack is executed.

Current vs. Expected behavior

Expected behavior
Dokploy should successfully download the railpack binary and continue the build process, or gracefully fall back to a compatible download command based on the available curl version.

Current behavior
The build fails immediately because the curl option --retry-all-errors is not supported by the curl version in the environment, resulting in exit code 2.
This failure happens before railpack is executed, but the error message incorrectly suggests a railpack platform compatibility issue.

Provide environment information

- Operating System: 
- NAME="Rocky Linux"

VERSION="8.4 (Green Obsidian)"
ID="rocky"
ID_LIKE="rhel fedora"
VERSION_ID="8.4"
PLATFORM_ID="platform:el8"
PRETTY_NAME="Rocky Linux 8.4 (Green Obsidian)"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:rocky:rocky:8.4:GA"
HOME_URL="https://rockylinux.org/"
BUG_REPORT_URL="https://bugs.rockylinux.org/"
ROCKY_SUPPORT_PRODUCT="Rocky Linux"
ROCKY_SUPPORT_PRODUCT_VERSION="8"

- Dokploy version: latest (at time of report)
- Deployment target: Same server where Dokploy is installed
- Application type: Nextjs.16 application (Railpack-based build)

Which area(s) are affected? (Select all that apply)

Application

Are you deploying the applications where Dokploy is installed or on a remote server?

Remote server

Additional context

The issue is caused by Dokploy assuming support for curl --retry-all-errors,
which was introduced in newer curl versions.

On systems with older curl versions (e.g. Rocky),
this option is unknown and causes the command to fail immediately.

This results in a misleading error message that points to railpack platform support,
even though the download step itself fails before railpack is used.

Suggested fixes:

• Remove --retry-all-errors, or
• Detect curl version before using this flag, or
• Add a fallback retry mechanism for older curl versions.

Will you send a PR to fix it?

Maybe, need help

[StruggleYang]

Deployment build logs:
.....

Installing railpack, please wait…
curl: option --retry-all-errors: is unknown
curl: try 'curl --help' or 'curl --manual' for more information
x Command failed (exit code 2): curl --fail --silent --location --retry 3 --retry-all-errors --retry-delay 2 --output /tmp/tmp.m56uvkFOBb-railpack.1768475335.tar.gz https://github.com/railwayapp/railpack/releases/download/v0.15.4/railpack-v0.15.4-x86_64-unknown-linux-musl.tar.gz
This is likely due to railpack not yet supporting your configuration.
If you would like to see a build for your configuration,
please create an issue requesting a build for x86_64-unknown-linux-musl:
https://github.com/railwayapp/railpack/issues/new/
Error occurred ❌, check the logs for details.