# Doppler masks underlying boot errors

**URL:** <https://community.doppler.com/t/doppler-masks-underlying-boot-errors/234>\
**Category:** Need Help\
**Created:** [June 8, 2021, 5:59pm UTC](https://community.doppler.com/t/doppler-masks-underlying-boot-errors/234 "2021-06-08T17:59:52Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![avaitla16](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/avaitla16/32/136_2.png) [@avaitla16](https://community.doppler.com/u/avaitla16)\
**Post date:** [June 8, 2021, 5:59pm UTC](https://community.doppler.com/t/doppler-masks-underlying-boot-errors/234/1 "2021-06-08T17:59:53Z")

</div>

Currently I use porter to run our docker containers. If I made a run command of:

```auto
python ... 

```

When the binary doesn’t exist I see the following error:

```auto
Error: failed to start container “job”: Error response from daemon: OCI runtime create failed: container_linux.go:367: starting container process caused: exec: “python”: executable file not found in $PATH: unknown

```

This is because I should be using python3. Now if I wrap this in doppler as follows:

```auto
doppler run -- python ...

```

I see no error any longer (literally nothing, simply fails), making it really challenging to see what went wrong.

If I add --debug to the run command I see the following:

```auto
Doppler Error: fork/exec : no such file or directory

```

This at least points out the issue is the python is the wrong binary, but definitely not an ideal error. FWIW we use the ubuntu20.04 docker base image (nothing fancy).

How can doppler spit out better error messages when the underlying run command fails so we can effectively troubleshoot.

---

<div class="post-metadata">

**Author:** ![thomasp](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/thomasp/32/785_2.png) [@thomasp](https://community.doppler.com/u/thomasp)\
**Post date:** [June 8, 2021, 6:44pm UTC](https://community.doppler.com/t/doppler-masks-underlying-boot-errors/234/2 "2021-06-08T18:44:07Z")

</div>

We’ve just released [Doppler CLI v3.26.1](https://github.com/DopplerHQ/cli/releases/tag/3.26.1) to address this issue. `doppler run` will now print the exit error if due to an inability to `exec` your provided command. Let me know if that adequately addresses your issue.

---

<div class="post-metadata">

**Author:** ![avaitla16](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/avaitla16/32/136_2.png) [@avaitla16](https://community.doppler.com/u/avaitla16)\
**Post date:** [June 8, 2021, 7:31pm UTC](https://community.doppler.com/t/doppler-masks-underlying-boot-errors/234/3 "2021-06-08T19:31:52Z")

</div>

Perfect thanks. Here’s the new error from doppler:

```auto
Doppler Error: exec: "python": executable file not found in $PATH

```