[bug]: docker setup additional space causes latest release to not get found by curl

[seannaesmb]

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

Using the docker steps and downloading the setup.sh script, running on Windows 11 fails. Noticing the VERSION is not set at all.

Steps to reproduce

1. Go to https://developers.plane.so/self-hosting/methods/docker-compose
2. Follow the instructions
3. Running the setup.sh file doesn't show effective pulling of docker components
4. Checking existing version fails [curl]

! deployments/cli/community/install.sh

• Space after "tag_name:"

(

plane/deployments/cli/community/install.sh

Line 60 in c3a9f99

local latest_release=$(curl -sSL https://api.github.com/repos/$GH_REPO/releases/latest | grep -o '"tag_name": "[^"]*"' | sed 's/"tag_name": "//;s/"//g')

)

Environment

Production

Browser

Google Chrome

Variant

Self-hosted

Version

v1.2.3

[makeplane]

Synced with Plane Workspace 🔄

[GIT-139] [bug]: docker setup additional space causes latest release to not get found by curl

[makeplane]

Synced with Plane Workspace 🔄

[GIT-138] [bug]: docker setup additional space causes latest release to not get found by curl

[akshat5302]

Hi @seannaesmb, this setup script may fail since Plane is supported on Linux-based systems, and you're running it on Windows 11. Could you please try it in WSL or any other linux machine and check if the issue still persists

Prerequisites:
https://developers.plane.so/self-hosting/methods/docker-compose#prerequisites

[HermessNRJ]

Hello, I just tested on an Ubuntu server, and I have the same problem. By removing the space in the regex after '"tag_name": it works (also need to remove it in the sed).

[akshat5302]

Thanks for confirming this. We will get that fixed in our upcoming community releases

[chrellrich]

As of https://github.com/makeplane/plane/releases/tag/v1.3.1 this issue still persists.

[akshat5302]

You were right about the space after "tag_name":, thanks for pinpointing it. The fix is in #9916. It accepts "tag_name": with or without a space, in both setup.sh and swarm.sh, and stops the script if the release lookup fails instead of carrying on with an empty version.

Workaround until the fix ships in a release: run this in the folder where you downloaded setup.sh, then run the installer again:

sed -i.bak 's/"tag_name": "/"tag_name": *"/g' setup.sh
./setup.sh

This makes the same change as the PR. We tested it on the setup.sh from the latest release (v1.4.2): the release lookup then returns v1.4.2. A backup of the original is left as setup.sh.bak.

The PR will close this issue when it merges. The fixed setup.sh reaches the docs install steps with the next Community release.