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.

Sign up for GitHub

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

Jump to bottom

Error creating mount with source ".../hostname": broken pipe: unknown. #1765

Closed
fvoznika opened this issue Feb 5, 2020 · 2 comments
Closed

Error creating mount with source ".../hostname": broken pipe: unknown. #1765

fvoznika opened this issue Feb 5, 2020 · 2 comments
Labels
area: container runtime Issue related to docker, kubernetes, OCI runtime area: integration Issue related to third party integrations stale-issue This issue has not been updated in 120 days. type: bug Something isn't working

Comments

@fvoznika
Copy link
Member

fvoznika commented Feb 5, 2020

This error can happen running any image with kernel between 5.1 and 5.3.15, 5.4.2, or 5.5. This happens because root runs with more strict RLIMIT_MEMLOCK limit. Go 1.14 attempts to mlock thread stacks to workaround a Linux kernel bug, trips over the limit, and dies. You'll find messages like these in the gofer log:

runtime: mlock of signal stack failed: 12
runtime: increase the mlock limit (ulimit -l) or
runtime: update your kernel to 5.3.15+, 5.4.2+, or 5.5+
fatal error: mlock failed

To workaround it, add the following line to the [Service] section in /lib/systemd/system/containerd.service:

LimitMEMLOCK=infinity

Then run: systemctl daemon-reload && systemctl restart containerd
@fvoznika fvoznika added area: container runtime Issue related to docker, kubernetes, OCI runtime type: bug Something isn't working labels Feb 5, 2020
ianlewis pushed a commit to google/gvisor-website that referenced this issue Mar 12, 2020
Add FAQ to website for Kernel bug issue.
bada6a6 
google/gvisor#1765
@ianlewis ianlewis mentioned this issue Mar 12, 2020
Merged
ianlewis pushed a commit to google/gvisor-website that referenced this issue Mar 15, 2020
Add FAQ to website for Kernel bug issue.
e024f8f 
google/gvisor#1765
@copybara-service copybara-service bot mentioned this issue Apr 8, 2020
Merged
copybara-service bot pushed a commit that referenced this issue Apr 8, 2020
@gvisor-bot
Add friendlier messages for frequently encountered errors.
56054fc 
Issue #2270
Issue #1765

PiperOrigin-RevId: 305385436
@ianlewis ianlewis added the area: integration Issue related to third party integrations label Aug 14, 2020
@github-actions
Copy link

A friendly reminder that this issue had no activity for 120 days.

@github-actions github-actions bot added the stale-issue This issue has not been updated in 120 days. label Sep 15, 2023
@ayushr2
Copy link
Collaborator

ayushr2 commented Sep 15, 2023

#151 and #2255 have added good docs and friendly messages. This is a kernel bug. Not sure what more we can do.

@ayushr2 ayushr2 closed this as completed Sep 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area: container runtime Issue related to docker, kubernetes, OCI runtime area: integration Issue related to third party integrations stale-issue This issue has not been updated in 120 days. type: bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ianlewis @fvoznika @ayushr2