On Wednesday, March 9, 2016 at 10:53:58 PM UTC+5:30, Chris Leech wrote: > > On Tue, Mar 08, 2016 at 02:54:29AM +0000, Serguei Bezverkhi (sbezverk) > wrote: > > Hello, > > > > As per Michael Christie suggestion, I am reaching out to a wider > > audience. I am trying to run iscsid inside of a Docker container but > > without using systemd. When I start iscsid -d 8 -f, it fails with > > "Cannot bind IPC socket". I would appreciate if somebody who managed > > to get it working, share his/her steps. > > You'll probably need to run it using dockers host mode networking, not > using a container specific network namespace. The iSCSI netlink control > code in the kernel is not network namespace aware, and can only be > accessed from the default/original network namespace (that's the IPC > socket). Not being able to use a new network namespace also means that > you can only run a single iscsid instance on the system. > > I had the start of a kernel patch series to deal with this posted a > while back. I never finished the sysfs object filtering by network > namespace for iSCSI, particularly moving the flash node db sysfs code > from bus to class devices to allow for namespace filtering was still an > open issue. > > - Chris > > Hi Chris,
Do you any latest update on this? Thanks. -- 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 open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at https://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
