From 3b0ee85e983ad1a9bcd953910ef2939b89681b8d Mon Sep 17 00:00:00 2001 From: Shaun Gowie Date: Thu, 3 May 2018 15:26:56 -0600 Subject: [PATCH] Removes errant space, adds newline at the end of the file. --- centos/content.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/centos/content.md b/centos/content.md index 365315a85..69710d6b3 100644 --- a/centos/content.md +++ b/centos/content.md @@ -85,7 +85,7 @@ This container is running with systemd in a limited context, with the cgroups fi ## A note about vsyscall -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. +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: @@ -105,4 +105,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/) \ No newline at end of file +Further reading : [lwn.net](https://lwn.net/Articles/446528/)