Remove boostrap password instructions for docker installs from setup flow

[richard-cox]

Is your feature request related to a problem? Please describe.

• Rancher can either be installed via dev only "docker" mode or via helm
• During setup we prompt users to find the bootstrap password
• Instructions are different per installation method (docker/helm)
• We show them both

Describe the solution you'd like

• as per conversation https://suse.slack.com/archives/C02AXMUQ4A1/p1779446562286659 remove the docker instructions entirely
• This avoids
  • advertising dev only docker
  • showing the unsupported docker mode instructions in Prime builds

Additional context

• conditional showing docker instructions was not chosen - Only show bootstrap password instructions relevant to install method #17789

[github-actions]

🎯 Agentic Issue Triage

Summary: This enhancement requests the removal of Docker-specific bootstrap password instructions from the Rancher setup/login flow. Since Docker mode is dev-only and unsupported in Prime builds, displaying those instructions is misleading and potentially confusing. The simpler fix (removing Docker instructions entirely) was chosen over the conditional approach rejected in #17789.

📍 Affected Code

The Docker bootstrap password instructions live in:

• shell/pages/auth/login.vue — contains the template section with both Helm (kubectl get secret ...bootstrapPassword...) and Docker (docker logs <container-id> 2>&1 | grep "Bootstrap Password:") instructions.

The relevant template block is around lines ~420–432 in login.vue. The kubectlCmd computed property (line ~131) constructs the Helm/kubectl command for copying.

🔧 Implementation Guidance

The change is straightforward:

1. Locate the <li> block in shell/pages/auth/login.vue containing the docker logs <container-id> <CopyCode> element and remove it (along with any surrounding Docker-specific heading or paragraph).
2. Remove any associated i18n keys related to Docker bootstrap instructions (search for docker keys in the locale files under shell/assets/translations/).
3. Remove the kubectlCmd computed property if it was Docker-specific, or keep/adapt it if it serves the Helm instructions.
4. Check for any unit tests covering this section of login.vue and update them accordingly.

Checklist:

• Remove the Docker docker logs ... instruction block from shell/pages/auth/login.vue
• Remove any Docker-specific i18n translation keys related to bootstrap password display
• Verify the Helm/kubectl bootstrap password instructions remain intact and correctly displayed
• Update or add unit tests in shell/pages/auth/__tests__/login.test.ts (if it exists) to assert Docker instructions are no longer rendered
• Verify the setup flow renders correctly in a local dev environment

🔗 Related Issues & Context

• Only show bootstrap password instructions relevant to install method #17789 (closed/not_planned) — The previous approach was to conditionally show instructions based on install method. This was rejected in favour of the simpler solution in this issue.
• Slack discussion referenced: `(suse.slack.com/redacted)

🧪 Testing Notes

• Manually verify the bootstrap password setup page no longer shows Docker-specific instructions.
• Verify Helm instructions still appear correctly.
• Check Prime builds specifically, since the Docker instructions were already problematic there.

Generated by Agentic Triage for issue #17792 · ● 376.6K · ◷

[github-actions]

🤖 Issue grooming questions

The problem statement is clear — the docker bootstrap password instructions should be removed from the setup flow to avoid advertising the dev-only docker install mode and to clean up the experience in Prime builds. The context and motivation are well described. One item is needed before this can be triaged for development.

Missing: Acceptance Criteria

Please add a concrete, testable checklist defining what "done" looks like. For example:

• During the setup flow, instructions for finding the bootstrap password via docker logs are no longer displayed.
• Helm-based bootstrap password instructions are still shown correctly.
• The setup flow behaves correctly in Prime builds (no docker-only instructions appear).
• Existing setup flow tests pass without modification (or are updated to reflect the removal).

This comment was generated automatically to help gather the information needed to groom this issue.

Generated by Daily Issue Grooming · ● 972.7K · ◷