Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Segmentation fault in docker on alpine
See original GitHub issueIssue
Impacted version: All
$ neofetch
.hddddddddddddddddddddddh. root@*
:dddddddddddddddddddddddddd: --------------
/dddddddddddddddddddddddddddd/ OS: Alpine Linux v3.6 x86_64
+dddddddddddddddddddddddddddddd+ Host: ProLiant DL360e Gen8
`sdddddddddddddddddddddddddddddddds` Kernel: 4.9.32-0-hardened
`ydddddddddddd++hdddddddddddddddddddy` Uptime: 2 days, 16 hours, 18 mins
.hddddddddddd+` `+ddddh:-sdddddddddddh. Packages: 182
hdddddddddd+` `+y: .sddddddddddh Shell: bash 4.3.48
ddddddddh+` `//` `.` -sddddddddd Terminal: /dev/pts/0
ddddddh+` `/hddh/` `:s- -sddddddd CPU: Intel Xeon E5-2450L 0 (32) @ 1.800GHz
ddddh+` `/+/dddddh/` `+s- -sddddd GPU: Matrox Electronics Systems Ltd. MGA G200EH
ddd+` `/o` :dddddddh/` `oy- .yddd Memory: 825MiB / 64295MiB
hdddyo+ohddyosdddddddddho+oydddy++ohdddh
.hddddddddddddddddddddddddddddddddddddh.
`yddddddddddddddddddddddddddddddddddy`
`sdddddddddddddddddddddddddddddddds`
+dddddddddddddddddddddddddddddd+
/dddddddddddddddddddddddddddd/
:dddddddddddddddddddddddddd:
.hddddddddddddddddddddddh.
docker run -it --rm -e "MONGO_URL=mongodb://mongo/wekan" --entrypoint bash --name wekan wekanteam/wekan:v0.50
ulimit -c 1024
node /build/main.js
# Segmentation fault (core dumped)
$ docker info
Containers: 11
Running: 10
Paused: 0
Stopped: 1
Images: 13
Server Version: 17.05.0-ce
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 9048e5e50717ea4497b757314bad98ea3763c145
runc version: 9c2d8d184e5da67c95d601382adf14862e4f2228
init version: 949e6facb77383876aeff8a6944dde66b3089574
Kernel Version: 4.9.32-0-hardened
Operating System: Alpine Linux v3.6
OSType: linux
Architecture: x86_64
CPUs: 32
Total Memory: 62.79GiB
Name: *
ID: E4ZN:SZMP:AVIO:GURT:IZ2R:I7X5:FLNV:DCST:ARNX:Y7MD:I7Q4:FK25
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
127.0.0.0/8
Registry Mirrors:
*
Live Restore Enabled: false
- Is this related https://github.com/sass/node-sass/issues/2031
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Segmentation fault in alpine Docker on M1 Mac #7402 - GitHub
Running parcel in an alpine Docker container on an M1 Mac results in a Segmentation Fault. Configuration (.babelrc, package.json, cli command).
Read more >Segmentation Fault in alpine docker image - Tor's Gitlab
Segmentation Fault in alpine docker image ... When running arti in the resulting container the program segfaults without any noticeable errors.
Read more >Docker alpine:3 Segmentation Fault - help - Rust Users Forum
I have strange problem. I've started write simple app. It runs on debian every time, also in docker containter with debian, but in...
Read more >Segmentation fault when trying to run Haxe on Alpine Linux ...
I'm new to Docker and I'm not a regular Linux user, but after some trial and error I've got Neko and Haxelib running...
Read more >Alpine fails to run my app - what steps should I take now? : r/rust
--target=x86_64-unknown-linux-musl inside an docker alpine… ... directly from the container thru sh is Segmentation fault (core dumped) .
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
I just meet the same problem arangodb.
The reason this problem comes up , is not relate to wekan, because nodejs mmap need PROT_EXEC, end pax enabled, this will failed.
Just add the pax header to nodejs(
paxctl -mC $(which node)), everything is fine now.@wenerme
Your fix is now merged to Wekan devel branch, and will be merged to master later and be included in Wekan by default.