Iscsid未在MacOS主机上的centos6扩展坞上启动

Question

我正在尝试在centos docker上运行iscsid。但命令失败，并显示"FATAL: the not load /lib/modules/4.9.13-moby/modules.dep: No the file or directory“

[root@7627d06541cc opt]# iscsiadm -m node -o new -T bilbo:cdisk0 -p 127.0.0.1
Starting iscsid: FATAL: Could not load /lib/modules/4.9.13-moby/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/4.9.13-moby/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/4.9.13-moby/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/4.9.13-moby/modules.dep: No such file or directory
                                                       [  OK  ]
iscsiadm: can not connect to iSCSI daemon (111)!
New iSCSI node [tcp:[hw=,ip=,net_if=,iscsi_if=default] 127.0.0.1,3260,-1 bilbo:cdisk0] added

Docker是用来启动的

msingh$ docker run -it cent6 bash

docker中的信息

[root@7627d06541cc opt]# uname -a
Linux 7627d06541cc 4.9.13-moby #1 SMP Sat Mar 25 02:48:44 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
[root@7627d06541cc opt]# ls /lib/modules/
2.6.32-642.13.1.el6.x86_64

我还尝试从创建软链接

[root@7627d06541cc opt]# ln -s /lib/modules/2.6.32-642.13.1.el6.x86_64 /lib/modules/4.9.13-moby

但是，iscsid仍然失败，因为

[root@7627d06541cc opt]# iscsiadm -m node -o new -T bilbo:cdisk0 -p 127.0.0.1
Starting iscsid: FATAL: Error inserting iscsi_tcp (/lib/modules/4.9.13-moby/kernel/drivers/scsi/iscsi_tcp.ko): Invalid module format
FATAL: Error inserting ib_iser (/lib/modules/4.9.13-moby/kernel/drivers/infiniband/ulp/iser/ib_iser.ko): Invalid module format
FATAL: Error inserting cxgb3i (/lib/modules/4.9.13-moby/kernel/drivers/scsi/cxgbi/cxgb3i/cxgb3i.ko): Invalid module format
FATAL: Error inserting cxgb4i (/lib/modules/4.9.13-moby/kernel/drivers/scsi/cxgbi/cxgb4i/cxgb4i.ko): Invalid module format
FATAL: Error inserting bnx2i (/lib/modules/4.9.13-moby/kernel/drivers/scsi/bnx2i/bnx2i.ko): Invalid module format
FATAL: Error inserting be2iscsi (/lib/modules/4.9.13-moby/kernel/drivers/scsi/be2iscsi/be2iscsi.ko): Invalid module format

Answer 1

--privileged应该解决这个问题。但是，您应该只使用docker run，而不是在docker构建过程中使用--privileged。

docker run --privileged -d --名称堆栈:最新