This repository was archived by the owner on Aug 18, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 82
chore: Add solution for Docker problems #369
Merged
Merged
Changes from 1 commit
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next
Next commit
chore: Add solution for Docker problems
- Loading branch information
commit 520f7070e37adecbb099ef3afb5b981e9b1a13a8
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
--- | ||
title: Docker problems | ||
description: Learn how to resolve issues related to Docker inside Coder workspaces. | ||
--- | ||
|
||
The kernel allocates a system key for each container created. When lots of developers | ||
are sharing the same instance, limits can be hit. | ||
|
||
> docker: Error response from daemon: OCI runtime create failed: | ||
container_linux.go:370: starting container process caused: | ||
process_linux.go:459: container init caused: join session keyring: | ||
create session key: disk quota exceeded: unknown. | ||
|
||
You can use a DaemonSet to apply the following values to increase the limits: | ||
|
||
``` | ||
sudo sysctl -w kernel.keys.maxkeys=20000 | ||
sudo sysctl -w kernel.keys.maxbytes=400000 | ||
``` |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
suggest we expand on this and add a daemonset example, we can reuse some of the content from the inotify watch limit doc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jawnsy Do you mind reviewing the content I added re: DaemonSets? I'm not super familiar w/ these so am open to all suggestions