Bump PID limit to 512 by default
This commit is contained in:
parent
08a7ccd175
commit
b618ec8877
|
@ -1,5 +1,9 @@
|
||||||
# Changelog
|
# Changelog
|
||||||
|
|
||||||
|
## v1.4.5
|
||||||
|
### Changed
|
||||||
|
* Upped the process limit for a container from `256` to `512` in order to address edge-cases for some games that spawn a lot of processes.
|
||||||
|
|
||||||
## v1.4.4
|
## v1.4.4
|
||||||
### Added
|
### Added
|
||||||
* **[security]** Adds support for limiting the total number of pids any one container can have active at once to prevent malicious users from impacting other instances on the same node.
|
* **[security]** Adds support for limiting the total number of pids any one container can have active at once to prevent malicious users from impacting other instances on the same node.
|
||||||
|
|
|
@ -60,7 +60,7 @@ type DockerConfiguration struct {
|
||||||
// at any given moment. This is a security concern in shared-hosting environments where a
|
// at any given moment. This is a security concern in shared-hosting environments where a
|
||||||
// malicious process could create enough processes to cause the host node to run out of
|
// malicious process could create enough processes to cause the host node to run out of
|
||||||
// available pids and crash.
|
// available pids and crash.
|
||||||
ContainerPidLimit int64 `default:"256" json:"container_pid_limit" yaml:"container_pid_limit"`
|
ContainerPidLimit int64 `default:"512" json:"container_pid_limit" yaml:"container_pid_limit"`
|
||||||
|
|
||||||
// InstallLimits defines the limits on the installer containers that prevents a server's
|
// InstallLimits defines the limits on the installer containers that prevents a server's
|
||||||
// installation process from unintentionally consuming more resources than expected. This
|
// installation process from unintentionally consuming more resources than expected. This
|
||||||
|
|
Loading…
Reference in New Issue
Block a user