Hi:

I'm trying to update open-iscsi, using Chris' patches as a starting place, 
so that it's network namespace aware, and hence could work in a docker 
container.

I will soon (I hope) be testing it in a container. So far, it seems to work 
using "ip netns exec".

Please see the RFC for patches I posted.

On Thursday, February 9, 2017 at 8:33:12 AM UTC-8 [email protected] 
wrote:

>
>
> 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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/open-iscsi/ef516f53-0ad8-4bc5-88d4-91730e2b480an%40googlegroups.com.

Reply via email to