<p>I'm trying to start kubernetes with an iscsi plugin inside rkt on CoreOS using the <a href="https://coreos.com/kubernetes/docs/latest/kubelet-wrapper.html#customizing-rkt-options" rel="nofollow">instruction here</a>. The problem is the iscsi daemon can't start, so I'm getting an error and can't mount the volume to the pod.</p>

<pre><code>iscsi_util.go:112] iscsi: failed to sendtargets to portal 156.64.48.59:3260 
    error: iscsiadm: Failed to load module tcp: No such file
iscsiadm: Could not load transport tcp.Dropping interface default.
[disk_manager.go:50] failed to attach disk 
iscsi: failed to setup
kubelet.go:1780] Unable to mount volumes for pod ...
</code></pre>

<p>I tried to mount the whole /dev/ inside the rkt container, but it doesn't help me.</p>

SerCe
<p>To get a working solution I had to: </p>

<ul>
<li><p>Change RKT options to</p>

<p>RKT_OPTS=--volume=iscsiadm,kind=host,source=/usr/sbin/iscsiadm --mount volume=iscsiadm,target=/usr/sbin/iscsiadm --volume=resolv,kind=host,source=/etc/resolv.conf --mount volume=resolv,target=/etc/resolv.conf --volume=etcs,kind=host,source=/etc/iscsi/ --mount volume=etcs,target=/etc/iscsi --volume=iscsid,kind=host,source=/usr/sbin/iscsid --mount volume=iscsid,target=/usr/sbin/iscsid</p></li>
<li><p><code>sudo modprobe iscsi_tcp</code></p></li>
</ul>

<p>Initialize tcp module in advance because <a href="https://github.com/open-iscsi/open-iscsi/blob/4c1f2d90ef1c73e33d9f1e4ae9c206ffe015a8f9/usr/transport.c#L196" rel="nofollow">it needed</a> for ascsiadm. But CoreOS loads modules "<a href="https://coreos.com/os/docs/latest/other-settings.html" rel="nofollow">as-needed</a>" and by some reasons it doesn't work inside rkt container. </p>

<ul>
<li><code>echo "InitiatorName=iqn.2001-12.com.mycompany:volume.openiscsi-initiator" &gt; /etc/iscsi/initiatorname.iscsi</code></li>
</ul>

<p>At least some initiator name <a href="https://github.com/open-iscsi/open-iscsi/blob/4c1f2d90ef1c73e33d9f1e4ae9c206ffe015a8f9/usr/discovery.c#L352" rel="nofollow">is needed</a>.</p>

<p>I also filled <a href="https://github.com/coreos/bugs/issues/1415" rel="nofollow">the bug</a> in CoreOS, maybe a better workaround exists.</p>
