<p dir="auto">Nodes Network when a minion node becomes unreachable [replication controller] recreates pods scheduled on the unreachable minion node AND allows scheduling of pods on a minion after it rejoins the cluster(Failed 17 times in the last 30 runs. Stability: 43 %)Failed with 0 retries</p>
<p dir="auto"><strong>Is this a request for help?</strong> (If yes, you should use our troubleshooting guide and community support channels, see <a href="http://kubernetes.io/docs/troubleshooting/" rel="nofollow">http://kubernetes.io/docs/troubleshooting/</a>.):</p>
<p dir="auto">No</p>
<p dir="auto"><strong>What keywords did you search in Kubernetes issues before filing this one?</strong> (If you have found any duplicates, you should instead reply there.):</p>
<p dir="auto">Docker privileged securitycontext</p>
<hr>
<p dir="auto"><strong>Is this a BUG REPORT or FEATURE REQUEST?</strong> (choose one):</p>
<p dir="auto">BUG REPORT</p>

<p dir="auto"><strong>Kubernetes version</strong> (use <code class="notranslate">kubectl version</code>):</p>
<p dir="auto">1.4.1</p>
<p dir="auto"><strong>Environment</strong>:</p>
<ul dir="auto">
<li><strong>Cloud provider or hardware configuration</strong>:</li>
<li><strong>OS</strong> (e.g. from /etc/os-release):</li>
<li><strong>Kernel</strong> (e.g. <code class="notranslate">uname -a</code>):</li>
<li><strong>Install tools</strong>:</li>
<li><strong>Others</strong>:</li>
</ul>
<p dir="auto">Linux m15 4.4.24-hypriotos-v7+ <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="35192559" data-permission-text="Title is private" data-url="https://github.com/kubernetes/kubernetes/issues/1" data-hovercard-type="issue" data-hovercard-url="/kubernetes/kubernetes/issues/1/hovercard" href="https://github.com/kubernetes/kubernetes/issues/1">#1</a> SMP PREEMPT Tue Oct 11 17:15:58 UTC 2016 armv7l GNU/Linux</p>
<p dir="auto"><strong>What happened</strong>:</p>
<p dir="auto">I have a Docker image that accesses /sys/devices. When I run the container by hand on that box using the following cmd, the application works as expected.</p>
<p dir="auto">docker run -it --privileged  fred</p>
<p dir="auto">However is I set up the same image under kubernetes using the following yaml, the application fail on the very same box.</p>
<p dir="auto">kind:       Deployment<br>
apiVersion: extensions/v1beta1<br>
metadata:<br>
name: fred<br>
spec:<br>
replicas: 1<br>
template:<br>
spec:<br>
containers:<br>
- name:  fred<br>
securityContext:<br>
privileged: true<br>
image: fred</p>
<p dir="auto"><strong>What you expected to happen</strong>:</p>
<p dir="auto">Setting the podSecurityContext privilege option works as if I ran the container with docker directly.</p>
<p dir="auto">Perhaps I am missing the intent here, but I was expecting this to work and if not what else do I need to specify to allow the container to access system level resources on the host machine.  I have tried setting the runAsUser to root but to no avail.</p>
<p dir="auto"><strong>How to reproduce it</strong> (as minimally and precisely as possible):</p>
<p dir="auto">Sadly not short way to repro + using private docker image</p>
<p dir="auto"><strong>Anything else do we need to know</strong>:</p>
<p dir="auto">I need to tell kubernetes that this container needs to run with the docker --privileged argument. How does one achieve this behavior.</p>