Terminal requires using bash but some containers uses sh

[davsclaus]

The base images for fabric8 java are shipped with sh and not bash. So you can only shell into them when using sh.

From the web console you get an error

Maybe we can try with bash first and if that fails then try sh ?

[gashcrumb]

We could also try not specifying a command, then you'll get whatever
default terminal is defined for the user account in that container, but
then it's also hard to know what shell you're using. That being said, are
we using a different base image these days for Java stuff?

On Thu, Sep 8, 2016 at 7:30 AM, Claus Ibsen [email protected]
wrote:

The base images for fabric8 java are shipped with sh and not bash. So you
can only shell into them when using sh.

From the web console you get an error

[image: screen shot 2016-09-08 at 1 28 34 pm]
https://cloud.githubusercontent.com/assets/477100/18347863/4e6655b6-75c8-11e6-8d29-29012fe4a5b6.png

Maybe we can try with bash first and if that fails then try sh ?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#216, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAVdrKprfBVSAdlX0Vkn97EjejNP2ne-ks5qn_G4gaJpZM4J344_
.

[davsclaus]

I think @rhuss knows best what base images are in use, and what shell they provide. I think there is some base images for community vs product.

[iscra]

Just noticed this issue in our cluster, happens for all Java projects.

Build with f8-maven-plugin, default image is currently fabric8/java-alpine-openjdk8-jdk based of Alpine 3.4, which does not have bash, just sh.

Making the command configurable in preferences would already help fast.

[ambition-consulting]

+1