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

More settings on docker containers instantiated by Cortex #387

Closed
To-om opened this issue Oct 29, 2021 · 0 comments
Closed

More settings on docker containers instantiated by Cortex #387

To-om opened this issue Oct 29, 2021 · 0 comments
Assignees
Milestone

Comments

@To-om
Copy link
Contributor

To-om commented Oct 29, 2021

Request Type

Feature Request

Work Environment

Cortex 3.1.1

Problem Description

The aim of this issue is to allow the administrator to configure how the docker containers are created. The available settings (in application.conf) are:

    docker.container.capAdd: (array of string) Add Linux capabilities
    docker.container.capDrop: (array of string) Drop Linux capabilities
    docker.container.cgroupParent: (string) Cgroup to run a container in
    docker.container.cpuPeriod: (integer) Limit the CPU CFS (Completely Fair Scheduler) period
    docker.container.cpuQuota: (integer) Limit the CPU CFS (Completely Fair Scheduler) quota
    docker.container.dns: (array of string) Set custom dns servers for the container
    docker.container.dnsSearch: (array of string) Search list for host-name lookup.
    docker.container.extraHosts: (array of string) Add a line to /etc/hosts (host:IP)
    docker.container.kernelMemory: (integer) Kernel memory limit
    docker.container.memoryReservation: (integer) Memory soft limit
    docker.container.memory: (integer) Memory limit
    docker.container.memorySwap: (integer) Total memory limit (memory + swap)
    docker.container.memorySwappiness: (integer) Tune a container’s memory swappiness behavior. Accepts an integer between 0 and 100
    docker.container.networkMode: (string) name of the network
    docker.container.privileged: (boolean) Give extended privileges to this container

Currently, this settings are global for all containers (all analyzers/responders)

@To-om To-om added this to the 3.1.2 milestone Oct 29, 2021
@To-om To-om self-assigned this Oct 29, 2021
To-om added a commit that referenced this issue Oct 29, 2021
@To-om To-om closed this as completed Oct 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant