@Clint,
Thanks. Then I see three possible workarounds:
1. The simplest way would be to have iscsid running on the host, and
connect to it over tcp from the container.
2. You could also have a container without its own network namespace,
and have iscsid running there.
3. You could open the netlink socket from the host network namespace,
and pass that into the container.
If none of these suffices, then I'll mark this as affecting the kernel,
and it'll take a new kernel feature to make this work. However
controlling host devices from a container is in general deemed
suboptimal (see user namespaces which may not access many devices at
all). To solve the netlink part of the issue we would have to come up
with a way to choose which containers may access the netlink socket.
It would still be useful for future consideration of this bug if you
could attach an strace of the netlink failure to this bug.
** Changed in: lxc (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1226855
Title:
Cannot use open-iscsi inside LXC container
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1226855/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
