Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

P1 Mode signal 11 on Ubuntu 19.04 #192

Closed
katakombi opened this issue Apr 20, 2019 · 8 comments
Closed

P1 Mode signal 11 on Ubuntu 19.04 #192

katakombi opened this issue Apr 20, 2019 · 8 comments

Comments

@katakombi
Copy link

katakombi commented Apr 20, 2019

When I run udocker from Ubuntu 19.04 with kernel 5.0 I get a Signal 11:

./udocker pull alpine:latest
./udocker create --name=a alpine:latest
./udocker run a sh
proot info: vpid 1: terminated with signal 11

This happens when P1 mode is being used. P2 still seems to work fine when forced using

export PROOT_NO_SECCOMP=1

Edit: there might be related issues proot-me/proot#106
Could someone please confirm or give further details?

@katakombi katakombi changed the title P2 Mode signal 11 on Ubuntu 19.04 P1 Mode signal 11 on Ubuntu 19.04 Apr 21, 2019
@jorge-lip
Copy link
Collaborator

This issue seems fixed in the devel branch.

@katakombi
Copy link
Author

Did you update the proot static binary? Gonna recheck...

@katakombi
Copy link
Author

Confirmed to be fixed! Congrats & thanks! I'd just be interested if the issue was with proot after all...

@jorge-lip
Copy link
Collaborator

Yes it was recompiled. The tarball used by the devel branch is newer.

@katakombi
Copy link
Author

Alas, proot didn't solve the underlying bug (probably proot-me/proot#106)
This issue can still occur on other kernels/distros. I found it on Fedora 31 with kernel 5.3.11. Useless to open issues for udocker, just adding this as a note!

@jorge-lip
Copy link
Collaborator

Hi,
Can you try with the latest development version

@katakombi
Copy link
Author

I don't have my VM with Fedora 31 any longer. So I'd test it but it might take a while...

@jorge-lip jorge-lip added this to the 1.1.4 milestone Jan 7, 2020
@fireflyHunter
Copy link

I am experiencing the same issue here with latest udocker, tried different images but all fail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants