Skip to content
This repository has been archived by the owner on Mar 28, 2018. It is now read-only.

sysctl handling not implemented #817

Closed
mcastelino opened this issue Apr 12, 2017 · 2 comments
Closed

sysctl handling not implemented #817

mcastelino opened this issue Apr 12, 2017 · 2 comments

Comments

@mcastelino
Copy link
Contributor

Docker supports setting namespaced kernel parameters at runtime, runc honors this. We do not honor the same and report success

docker run --runtime=cor --sysctl net.ipv4.ip_forward=1 -it alpine sh
/ # sysctl net.ipv4.ip_forward
net.ipv4.ip_forward = 0

docker run --runtime=runc --sysctl net.ipv4.ip_forward=1 -it alpine sh
/ # sysctl net.ipv4.ip_forward
net.ipv4.ip_forward = 1
@mcastelino
Copy link
Contributor Author

mcastelino commented Apr 12, 2017

Note that we can actually support the setting of more kernel configuration variables with clear containers as we have an independent instance of the kernel running inside the virtual machine. However we also need to communicate that the sysctl settings for Clear Containers are not propagated from the host.

This non propagation will matter in the case of kubernetes (https://kubernetes.io/docs/concepts/cluster-administration/sysctl-cluster/) where certian unsafe sysctl settings can be safely performed in the case of clear containers.

Also there are some parameters that are not namespaced for example

sysctl -w net.bridge.bridge-nf-call-arptables=0
which is not namespaced today even though they are under net which is namespaced.

@sameo
Copy link

sameo commented May 11, 2017

This issue was moved to containers/virtcontainers#246

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants