github/kata-containers
1
0
Fork 1
mirror of https://github.com/kata-containers/kata-containers.git synced 2025-06-19 12:14:11 +00:00
Code Issues Projects Releases Wiki Activity

docs: Remove docker support with kata 2.x and sysctls

Browse Source 
Currently in kata 2.x, we do not have docker support, this PR removes
the docker documentation with sysctls.

Fixes #2029

Signed-off-by: Gabriela Cervantes <gabriela.cervantes.tellez@intel.com>
This commit is contained in:
Gabriela Cervantes 2021-06-14 14:20:14 -05:00
parent 9d585935b5
commit 601e2b65c5
1 changed files with 5 additions and 27 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
docs/how-to/how-to-use-sysctls-with-kata.md
View File

@ -16,11 +16,10 @@ To get a complete list of kernel parameters, run:
$ sudo sysctl -a $ sudo sysctl -a
``` ```
Both Docker and Kubernetes provide mechanisms for setting namespaced sysctls. Kubernetes provide mechanisms for setting namespaced sysctls.
Namespaced sysctls can be set per pod in the case of Kubernetes or per container Namespaced sysctls can be set per pod in the case of Kubernetes.
in case of Docker.
The following sysctls are known to be namespaced and can be set with The following sysctls are known to be namespaced and can be set with
Docker and Kubernetes: Kubernetes:
- `kernel.shm*` - `kernel.shm*`
- `kernel.msg*` - `kernel.msg*`
@ -30,31 +29,10 @@ Docker and Kubernetes:
### Namespaced Sysctls: ### Namespaced Sysctls:
Kata Containers supports setting namespaced sysctls with Docker and Kubernetes. Kata Containers supports setting namespaced sysctls with Kubernetes.
All namespaced sysctls can be set in the same way as regular Linux based All namespaced sysctls can be set in the same way as regular Linux based
containers, the difference being, in the case of Kata they are set inside the guest. containers, the difference being, in the case of Kata they are set inside the guest.
#### Setting Namespaced Sysctls with Docker:
```
$ sudo docker run --runtime=kata-runtime -it alpine cat /proc/sys/fs/mqueue/queues_max
256
$ sudo docker run --runtime=kata-runtime --sysctl fs.mqueue.queues_max=512 -it alpine cat /proc/sys/fs/mqueue/queues_max
512
```
... and:
```
$ sudo docker run --runtime=kata-runtime -it alpine cat /proc/sys/kernel/shmmax
18446744073692774399
$ sudo docker run --runtime=kata-runtime --sysctl kernel.shmmax=1024 -it alpine cat /proc/sys/kernel/shmmax
1024
```
For additional documentation on setting sysctls with Docker please refer to [Docker-sysctl-doc](https://docs.docker.com/engine/reference/commandline/run/#configure-namespaced-kernel-parameters-sysctls-at-runtime).
#### Setting Namespaced Sysctls with Kubernetes: #### Setting Namespaced Sysctls with Kubernetes:
Kubernetes considers certain sysctls as safe and others as unsafe. For detailed Kubernetes considers certain sysctls as safe and others as unsafe. For detailed
@ -100,7 +78,7 @@ spec:
### Non-Namespaced Sysctls: ### Non-Namespaced Sysctls:
Docker and Kubernetes disallow sysctls without a namespace. Kubernetes disallow sysctls without a namespace.
The recommendation is to set them directly on the host or use a privileged The recommendation is to set them directly on the host or use a privileged
container in the case of Kubernetes. container in the case of Kubernetes.