Repository navigation
Conversation
narcisonunez
approved these changes
Nov 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
install.sh(install andupdate) now shows clear progress instead of raw command output, when it runs in a terminal:[3/9]), each with a spinner and then a one-line result: a detail such as the Docker version or the advertise address, plus the time taken for slow steps.get.docker.comgoes to/var/log/dokploy-install.log. The file is mode 600 and appended on every run. If/var/logisn't writable, it uses a temp file instead; if no log file can be written at all, output streams as before.NO_COLORis respected.When output is not a terminal (CI, redirected to a file), command output streams as before, under plain
[n/9]step headers, and the final messages keep their original wording.What did not change
DOKPLOY_VERSION,ADVERTISE_ADDR,DOCKER_SWARM_INIT_ARGSandENDPOINT_MODE, plus Proxmox LXC detection./etc/dokploykeeps the same permissions.sh, socurl … | shkeeps working whereshis dash.DOKPLOY_VERSIONsupport is kept, so the pinned copy it builds is unaffected.docker --versioncall to show which version was found.Testing
docker,curl,ss,ip,opensslandapt-markcommands that record every call. Each scenario ran with the old and the new script, both piped and in a TTY, and produced the same calls in the same order and the same exit codes.ENDPOINT_MODE=dnsrr; customDOCKER_SWARM_INIT_ARGS;ADVERTISE_ADDR;DOKPLOY_VERSION=canary; GitHub unreachable; port 80 in use;docker swarm initfailing; the PostgreSQL service failing; an unsupported distro; a full disk; not running as root;update;updatewith a full disk.dash -npasses, and ShellCheck (-s sh) reports no new findings compared with the current script.The repo's CI doesn't check shell scripts, so these checks were run by hand.
Screenshots
Before:

After:
