java feature fails to install #1582

Activity

1. jakub-bochenski commented on Feb 18, 2026

   

   jakub-bochenski

   on Feb 18, 2026

   Author

   More actions

   A workaround is to set the default shell when creating you user:

   useradd --system --create-home --uid 500 --gid 500 --shell /bin/bash ${USERNAME}
   

   But a real fix would be to select bash as shell for su -c if you need the shell to be bash
2. jakub-bochenski

   added 2 commits that reference this issue on Feb 18, 2026

   fix: Set passwd shell to /bin/bash

   ...

   192d3ac

   fix: Set passwd shell to /bin/bash

   ...

   beed0d0
3. Matt Olson (mattolson)

   added a commit that references this issue on Feb 19, 2026

   fix: Set passwd shell to /bin/bash

   ...

   0f4a21b
4. Kaniska (v-Kaniska244)

   self-assigned this

   on Feb 19, 2026
5. jakub-bochenski

   added a commit that references this issue on Feb 19, 2026

   fix: Set passwd shell to /bin/bash

   ...

   44b851a
6. v-Kaniska244 commented on Mar 9, 2026

   

   Kaniska (v-Kaniska244)

   on Mar 9, 2026

   Contributor

   More actions

   Hi jakub-bochenski

   Thank you for reporting this issue. As its mentioned here, bash shell is actually required for the platform to install the java dev container feature.
7. jakub-bochenski commented on Mar 9, 2026

   

   jakub-bochenski

   on Mar 9, 2026

   Author

   More actions

   Thanks for the clarification. I understand that bash is required by the feature scripts.

   However, the issue here isn’t that bash is unavailable — it’s that the script invokes su -c without specifying the shell. In that case, the command is executed using the target user's login shell. If that shell is /bin/sh, the script ends up sourcing sdkman-init.sh with sh, which fails because it contains bash-specific syntax (source, [[ ]], etc.).

   So even when bash is installed, the install step can still fail depending on the user's configured shell.

   One workaround is to create the user with /bin/bash as the login shell:

   useradd --system --create-home --uid 500 --gid 500 --shell /bin/bash ${USERNAME}
   

   But a more robust fix would be to explicitly run the command with bash when using su -c, for example:

   su - ${USERNAME} -s /bin/bash -c "<command>"
   

   or

   su - ${USERNAME} -c "bash -lc '<command>'"
   

   That would ensure the feature works regardless of the user's default shell.

   👍React with 👍4Reacted by Myroslav, Philip Wedemann, nikekson and Natan

   👀React with 👀1Reacted by Kaniska