# I have several executables that just don't run on your build system (under docker), and no way I can see to debug

**URL:** <https://travis-ci.community/t/i-have-several-executables-that-just-dont-run-on-your-build-system-under-docker-and-no-way-i-can-see-to-debug/7693>\
**Category:** Windows\
**Created:** [March 21, 2020, 8:42pm UTC](https://travis-ci.community/t/i-have-several-executables-that-just-dont-run-on-your-build-system-under-docker-and-no-way-i-can-see-to-debug/7693 "2020-03-21T20:42:53Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\
**Post date:** [March 21, 2020, 9:29pm UTC](https://travis-ci.community/t/i-have-several-executables-that-just-dont-run-on-your-build-system-under-docker-and-no-way-i-can-see-to-debug/7693/2 "2020-03-21T21:29:13Z")

</div>

There’s always exit status of the last script statement, in `$?` Bash special variable:

```auto
docker exec --workdir c:/Stroika buildContainer sh -c "cd ThirdPartyComponents/WIX/CURRENT/ && ./candle -v; echo $?"

```

Depending on what product and its version `sh` in your container belongs to, it may or may not be able to automatically add “.exe” to searched name if you omit it in the command.

Anything beyond that can only be devised from the exit code: Windows has a few standard exit codes for when a process fails to start.

* * *

The `Error 127` and following messages actually belong to the `make` command above, due to [Stderr output is shown after the build log rather than inline](https://travis-ci.community/t/stderr-output-is-shown-after-the-build-log-rather-than-inline/5124).

---

_[View the full topic](https://travis-ci.community/t/i-have-several-executables-that-just-dont-run-on-your-build-system-under-docker-and-no-way-i-can-see-to-debug/7693)._