|
|
@@ -85,7 +85,7 @@ This container is running with systemd in a limited context, with the cgroups fi
|
|
|
|
|
|
## A note about vsyscall
|
|
|
|
|
|
-Legacy CentOS binaries and/or libraries are built to expect some system calls to be accessed via `vsyscall` mappings. Some linux distributions have opted to disable `vsyscall` entirely (opting exclusively for more secure `vdso` mappings), causing segmentation faults.
|
|
|
+CentOS 6 binaries and/or libraries are built to expect some system calls to be accessed via `vsyscall` mappings. Some linux distributions have opted to disable `vsyscall` entirely (opting exclusively for more secure `vdso` mappings), causing segmentation faults.
|
|
|
|
|
|
If running `docker run --rm -it centos:centos6.7 bash` immediately exits with status code `139`, check to see if your system has disabled vsyscall:
|
|
|
|
|
|
@@ -104,4 +104,4 @@ ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsysca
|
|
|
|
|
|
If you do not see a `vsyscall` mapping, and you need to run a legacy CentOS container, try adding `vsyscall=emulated` to the kernel options in your bootloader
|
|
|
|
|
|
-Further reading : [lwn.net](https://lwn.net/Articles/446528/)
|
|
|
+Further reading : [lwn.net](https://lwn.net/Articles/446528/)
|
Shaun Gowie