But this change required some changes on how the container run command is get. Until now, azk used /bin/sh -c by default in order to run any command inside a container. However, in cases which the Docker image set a custom CMD[...], this custom command was ignored and the behavior was different from the expected.
The consequences of this change is:
For systems run on azk start, /bin/sh -c is not used (forced) anymore. Instead, the priority is: "property command defined in Azkfile.js" > "command defined by CMD[...] in the Docker image";
For the command azk shell, the priority is: "option --shell passed to azk shell" > "property shell defined in Azkfile.js" > "command defined in CMD [...] in the Docker image" > "/bin/sh";
The command azk shell offers two options to run commands:
But this change required some changes on how the container run command is get. Until now,
azkused/bin/sh -cby default in order to run any command inside a container. However, in cases which the Docker image set a customCMD[...], this custom command was ignored and the behavior was different from the expected. The consequences of this change is:azk start,/bin/sh -cis not used (forced) anymore. Instead, the priority is: "propertycommanddefined inAzkfile.js" > "command defined byCMD[...]in the Docker image";azk shell, the priority is: "option--shellpassed toazk shell" > "propertyshelldefined inAzkfile.js" > "command defined inCMD [...]in the Docker image" > "/bin/sh";azk shelloffers two options to run commands: