# Serialport use leads to segmentation fault when using docker

**URL:** <https://discourse.nodered.org/t/serialport-use-leads-to-segmentation-fault-when-using-docker/69487>\
**Category:** General\
**Tags:** docker\
**Created:** [24 October 2022 11:01 UTC](https://discourse.nodered.org/t/serialport-use-leads-to-segmentation-fault-when-using-docker/69487 "2022-10-24T11:01:47Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [24 October 2022 11:37 UTC](https://discourse.nodered.org/t/serialport-use-leads-to-segmentation-fault-when-using-docker/69487/2 "2022-10-24T11:37:41Z")

</div>

I assume you realise the serial node uses `C` bindings and requires either the correct binaries or compilation on the guest?

Does your image have the necessary tools installed to compile the serial port?

See this issue: [serialport@10.3.0 fails in docker container on rpi · Issue #2438 · serialport/node-serialport · GitHub](https://github.com/serialport/node-serialport/issues/2438#issuecomment-1076374277) - might be relevant.

---

_[View the full topic](https://discourse.nodered.org/t/serialport-use-leads-to-segmentation-fault-when-using-docker/69487)._