Skip to content

Commit ed82e00

Browse files
committed
adding troubleshooting for debian issue apptainer/singularity#845
1 parent af2770d commit ed82e00

1 file changed

Lines changed: 29 additions & 0 deletions

File tree

pages/docs/overview/faq.md

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -256,6 +256,35 @@ You can read more about the Singularity <a href="/docs-security">security overvi
256256

257257
A little bit of help.
258258

259+
@gmkurtzer I'll get us started here, and if you want to edit / adjust I can add to our troubleshooting docs. Here is a first go not following this issue closely:
260+
261+
### Segfault on Bootstrap of Centos Image
262+
If you are bootstrapping a centos 6 docker image from a debian host, you might hit a segfault:
263+
264+
```
265+
$ singularity shell docker://centos:6
266+
Docker image path: index.docker.io/library/centos:6
267+
Cache folder set to /home/jbdenis/.singularity/docker
268+
Creating container runtime...
269+
Singularity: Invoking an interactive shell within container...
270+
271+
Segmentation fault
272+
```
273+
274+
The fix is on your host, you need to pass the variable `vsyscall=emulate` to the kernel, meaning in the file `/etc/default/grub` (note, this file is debian specific), add the following:
275+
276+
```
277+
GRUB_CMDLINE_LINUX_DEFAULT="vsyscall=emulate"
278+
```
279+
280+
and then update grub and reboot:
281+
282+
```
283+
update-grub && reboot
284+
```
285+
286+
For more information, see the <a href="https://github.com/singularityware/singularity/issues/845" target="_blank">original issue</a>.
287+
259288

260289
### How to use Singularity with GRSecurity enabled kernels
261290

0 commit comments

Comments
 (0)