<p>my containers are killed on a new installation of Fedora 24 atomic:</p>

<pre><code>#docker run -ti nginx /bin/bash

docker: Error response from daemon: Cannot start container f24104b29f7f1f1614024414e8346e1a98c722c027f4122e6c70f7ace0cc5353: [9] System error: exit status 1.
</code></pre>

<p>After some debugging session, I think the process gets killed right after trying to assign an address on network bridge (see docker daemon logs in the next links). But I have no idea why is that nor how to debug further.</p>

<p>Some additional info is reported here:</p>

<ul>
<li>SELinux is disabled:

<ul>
<li>bash-4.3# getenforce -> Permissive</li>
</ul></li>
<li>docker <a href="https://gist.github.com/mrceresa/f7cb3bc42958f5446b7baf2aa0246df5#file-gistfile1-txt" rel="nofollow noreferrer">info</a> </li>
<li>docker daemon log in <a href="https://gist.github.com/mrceresa/895efaefe14c89298ee75a56ad8bb6e7#file-docker-d" rel="nofollow noreferrer">debug</a> mode. At line 9 it receives the KILL signal.</li>
</ul>

<p>Any help would really be appreciated!</p>

<p>Best,</p>

<p>Mario</p>

<p>I've just found the problem:
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1320601" rel="nofollow noreferrer">https://bugzilla.redhat.com/show_bug.cgi?id=1320601</a></p>

<p>Adding the systemd flag to the launch script of the daemon:
--exec-opt native.cgroupdriver=systemd</p>

<p>solved the problem.</p>

<p>Thanks, Federkun, for help!</p>

<p>Best,</p>

<p>Mario</p>
