Docker for Mac (17.10.0-ce-mac36) segfaults on debian:wheezy/centos:6 images

[welps]

Expected behavior

Running docker run debian:wheezy returns exit code 0

Actual behavior

Running docker run debian:wheezy returns exit code 139

Information

Diagnostic ID: B3DEF8E-B246-47B7-A218-380229307B77
Docker for Mac: version: 17.10.0-ce-mac36 (a38d9cd48bd0ee31ec82c59b783aa2f2817bfb92)
macOS: version 10.13 (build: 17A405)
logs: /tmp/6B3DEF8E-B246-47B7-A218-380229307B77/20171024-190910.tar.gz
[OK] db.git
[OK] vmnetd
[OK] dns
[OK] driver.amd64-linux
[OK] virtualization VT-X
[OK] app
[OK] moby
[OK] system
[OK] moby-syslog
[OK] db
[OK] env
[OK] virtualization kern.hv_support
[OK] slirp
[OK] osxfs
[OK] moby-console
[OK] logs
[OK] docker-cli
[OK] menubar
[OK] disk

Steps to reproduce the behavior

1. Run docker run debian:wheezy
2. Check exit code

Other images that segfault:

• centos:6 - centos:6.9

[lipchyk]

Same here... Got the segfault on docker run redis:3.0.2

[cs96and]

Same issue on Windows as well
docker/for-win#1245

[welps]

@yspro Yeah anything derived from these base images will segfault. Happened to me with mongo.

[djs55]

Thanks for the report. The problem is a missing vsyscall=emulate argument on the kernel command-line which prevents some older binaries from working. There's a fix in the master branch which will be in the next edge release, due at the end of October. In the meantime I recommend working around the problem by switching either to the stable channel or the previous edge build 17.09.0-ce-mac34

[gtardif]

This should now work with latest edge version, released today (17.11.0-ce-rc2-mac37)

[welps]

I can confirm this has been fixed. Thanks!

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked