# Signals and balenaOS containers/services

**URL:** <https://forums.balena.io/t/signals-and-balenaos-containers-services/12139>\
**Category:** balenaOS\
**Created:** [May 28, 2019, 7:54pm UTC](https://forums.balena.io/t/signals-and-balenaos-containers-services/12139 "2019-05-28T19:54:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jason10](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/jason10/32/1464_2.png) [@jason10](https://forums.balena.io/u/jason10)\
**Post date:** [May 28, 2019, 7:54pm UTC](https://forums.balena.io/t/signals-and-balenaos-containers-services/12139/1 "2019-05-28T19:54:50Z")

</div>

This discussion of signals and processes has the following suggestions:

- Use the exec/JSON array form of `ENTRYPOINT` .
- Use `exec` in shell entrypoints.
- Don’t pipe your application’s output.
- Avoid being PID 1.
- Listen for `SIGTERM` or set `STOPSIGNAL` in your Dockerfile.

Do these suggestions apply to our balenalib based containers?

> **[Homepage of Hynek Schlawack](https://hynek.me/articles/docker-signals/)**
>
> Pythonista, Gopher, and speaker from Berlin/Germany.

---

<div class="post-metadata">

**Author:** ![samothx](https://avatars.discourse-cdn.com/v4/letter/s/c89c15/32.png) [@samothx](https://forums.balena.io/u/samothx)\
**Post date:** [May 28, 2019, 8:07pm UTC](https://forums.balena.io/t/signals-and-balenaos-containers-services/12139/2 "2019-05-28T20:07:09Z")

</div>

Hi Jason,  
thanks for posting that article - a very good explanation of the issues around signal handling in docker. I am pretty sure this applies to balena as well although I would have to talk to the developers for some of the details.  
Regards Thomas