Bleno segmentation fault in Docker container
See original GitHub issueI have a simple Docker container for Bleno, but when I run node main.js
with a basic main.js such as ‘var bleno = require(‘bleno’);’ it core dumps…
# node
> require('bleno');
Segmentation fault (core dumped)
Of course, it used to work 😉 Any idea?
To reproduce the issue, I provide my Dockerfile & commands. (of course, docker is required). This is my Dockerfile:
FROM node:latest
# Install bleno and dependencies ---------------
# bluetooth IS required despite we do service bluetooth stop in the end
RUN DEBIAN_FRONTEND=noninteractive apt-get update && \
apt-get install -yqq \
build-essential \
bluetooth \
bluez \
emacs \
libbluetooth-dev \
libudev-dev \
usbutils \
&& rm -rf /var/lib/apt/lists/*
RUN npm install bleno
WORKDIR /root
# Cleaning up and final setup -------------------------
RUN apt-get autoremove -yqq
RUN apt-get clean
RUN service bluetooth stop
To build it: docker build -t cryptax/bleno:test .
To run it: docker -it --rm --privileged cryptax/bleno:test /bin/bash
and then in the shell:
# node
> require('bleno');
Issue Analytics
- State:
- Created 6 years ago
- Comments:6
Top Results From Across the Web
Segmentation fault while running python in docker container
When I build Docker containers to install it, it does not ends on python cascade.py -vv when running the below shell script from...
Read more >Segmentation Fault in Linux Containers (exit code 139)
Segmentation faults are an unfortunate reality of software development. In this post you'll learn about the SIGSEGV error, and how to debug it...
Read more >Segmentation fault no matter what i have in my Dockerfile - Fly.io
I've been trying to fix this for 6 hours straight and I'm very frustrated. 1 Like. mkdir broken on Docker remote builder using...
Read more >Serialport use leads to segmentation fault when using docker
I assume you realise the serial node uses C bindings and requires either the correct binaries or compilation on the guest? Thank you...
Read more >Untitled
Hyundai accent era crash test, Brd gleich deutsches reich, ... Spongebob meme don't you squidward, Haidingergasse 23, Container basculante, Daveryon, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
running docker in network host mode solved issue for me. sudo docker run --privileged --rm -it --network host --name noble noble
This does not seem to be fixed yet. Using sandeepmistry/bleno made things better but did not resolve the issue. With latest node version (8.2.1) things got worse again. Any chance you work on a fix for node 6.11.2 ?