You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 11, 2023. It is now read-only.
Since a long time I was wondering why a docker container is able to see all cpu cores even if I limit it to e.g. one core. On my previous CentOS machine I was able to tweak many things and used some kernel patches. Now I am using RancherOS since several months. Now I stumbled over the same problem again but in RancherOS. I am using Rancher 2.0 to handle my containers. It doesn't matter if I create a container with the command and limit its resources or if I create the container in the Rancher webinterface.
is that right the way it is? I am not shure what exactly I've tweaked on CentOS but here is a Github issue thread I've found where people taled about simular situations. moby/moby#20770
The text was updated successfully, but these errors were encountered:
**RancherOS Version: 1.4.1
**Where are you running RancherOS? baremetal
Since a long time I was wondering why a docker container is able to see all cpu cores even if I limit it to e.g. one core. On my previous CentOS machine I was able to tweak many things and used some kernel patches. Now I am using RancherOS since several months. Now I stumbled over the same problem again but in RancherOS. I am using Rancher 2.0 to handle my containers. It doesn't matter if I create a container with the command and limit its resources or if I create the container in the Rancher webinterface.
is that right the way it is? I am not shure what exactly I've tweaked on CentOS but here is a Github issue thread I've found where people taled about simular situations.
moby/moby#20770
The text was updated successfully, but these errors were encountered: