Thanks for the reply. We are facing issues when we run iscsiadm in the container and iscsid on the host. At that time, iscsiadm can't reach to iscsid at all and all iscsiadm commands fail.
If we run iscsiadm and iscsid in the same container, it works but we don't know if this is how it is designed to run. So few specific questions; 1. If we run iscsid in container, do we need to shut the the iscsid that is running on host? 2. iscsid running in the container, requires kernel module iscsi_tcp to be part of the container image. Is this ok? 3. What is the standard topology for dealing with iscsi from containerized environments? Appreciate your help here. Thanks, Shailesh. On Wednesday, October 24, 2018 at 1:28:11 PM UTC-7, The Lee-Man wrote: > > Sorry, I should have asked: what issues have you experienced with > containers? > > On Wednesday, October 24, 2018 at 1:27:43 PM UTC-7, The Lee-Man wrote: >> >> On Tuesday, October 23, 2018 at 9:03:01 AM UTC-7, Shailesh Mittal wrote: >>> >>> Hi there, >>> >>> I understand that it was the topic of discussion earlier. As containers >>> are getting used more and more to run applications, there are frameworks >>> like Kubernetes (and more) where the calls to talk to scsi storage devices >>> are being made through a container. >>> >>> Here, vendors are in flux as they need to execute iscsiadm commands to >>> connect their iscsi based storage to the application-containers. These >>> caller modules (responsible for connecting to the remote storage) are >>> running in the containers and thus have no choice but executing iscsiadm >>> commands from the containers itself. >>> >>> Is there a well understood way to implement this? I remember the thread >>> from Chris Leech talking about containerizing iscsid but not sure the >>> end-result of that. ( >>> https://groups.google.com/forum/#!msg/open-iscsi/vWbi_LTMEeM/NdZPh33ed0oJ >>> ) >>> >>> Any help/direction here is much appreciated. >>> >>> Thanks, >>> Shailesh Mittal. >>> >> >> I have never messed with containers w/r/t iscsi, but I was under the >> impression Chris got this working. @Chris >> > -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
