Skip to content

Installation Docs: bash bootstrap.sh Command Conflicts with Dokku Installer File #26

Description

@mark-john-ignacio

Title: Installation Docs: bash bootstrap.sh Command Conflicts with Dokku Installer File

Body:

Hi there,

I encountered an issue following the "Install Using Script" documentation at https://shokku.dev/docs/installation that can be confusing, especially for users less familiar with Linux file handling.

Problem:

The official Dokku installation process (wget https://dokku.com/install/.../bootstrap.sh) downloads a script named bootstrap.sh, often into the /root/ directory or wherever the user runs the command.

Subsequently, following the Shokku installation instructions:

wget "https://shokku.dev/bootstrap.sh"
# export SHOKKU_LETSENCRYPT_EMAIL="foo@example.com" # (Assuming global email is set)
bash bootstrap.sh

Causes a problem:

  1. The wget "https://shokku.dev/bootstrap.sh" command downloads the Shokku installer.
  2. Because bootstrap.sh (from the Dokku install) already exists in the directory, wget automatically renames the new Shokku script to bootstrap.sh.1.
  3. The final documented command, bash bootstrap.sh, then executes the original Dokku installation script again, not the intended Shokku script (bootstrap.sh.1).

Steps to Reproduce:

  1. Install Dokku using the official bootstrap script, downloading bootstrap.sh to a directory (e.g., /root/).
  2. In the same directory, run wget "https://shokku.dev/bootstrap.sh".
  3. Observe that the file is saved as bootstrap.sh.1.
  4. Run the documented command bash bootstrap.sh.
  5. Observe that the Dokku installation process/checks run, not the Shokku installation.

Expected Behavior:

The documented commands should result in the Shokku installation script being executed.

Actual Behavior:

The documented bash bootstrap.sh command runs the previously downloaded Dokku installer script due to the filename collision and automatic renaming by wget.

Consequences:

This is confusing and led to significant troubleshooting time (in my case, I initially thought it was a server resource issue). Users might repeatedly run the Dokku installer or not realize why Shokku isn't installing.

Suggested Solution:

Could the documentation please be updated to account for this likely filename conflict? Perhaps:

  • Add a note warning users about the potential conflict.
  • Instruct users to check if the file was saved as bootstrap.sh.1 and run bash bootstrap.sh.1 if necessary.
  • Alternatively, suggest downloading the Shokku script with a different name using wget -O shokku_bootstrap.sh "...".

Thanks for providing Shokku!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions