Default `cmd` and shell type


We are rolling out a change to remove the default cmd from the base image (the first image listed in containerInfo) and overwrite it with /bin/bash -e and fallback to /bin/sh -e.

How does this impact me?

You no longer need to worry about your build exiting with status 137. One would see that after having a cmd on the base image that would execute alongside the commands you wanted to run.

Using set -e is now implied on each build but can be overwritten simply by specifying the shell type.

Kill signal problem