-
Notifications
You must be signed in to change notification settings - Fork 70
wshd can't run in clear container #342
Comments
Hi @wuzhy
in the logs makes me think of an issue of 9pfs with unlinked files (see intel/cc-oci-runtime#152) for a similar thread. In that case, we verified the issue by using a tmpfs on /tmp to see if that worked around the problem:
I don't see how |
@grahamwhaley Yes, the dir /share is mounted via docker run ... -v /root/wsh/share:/share .... hyperShared on /share type 9p (rw,sync,dirsync,nodev,relatime,trans=virtio) The original files or directory in /share can't seen by us now. |
@wuzhy what do you mean by "now" ? You have seen a recent change ? |
@sboeuf i mean that after the command "mount -t ramfs -o size=20M ramfs /share" is done, there is no files or directory under the dir "/share". |
@grahamwhaley yes, it can workaround with the help of your mentioned method. But has this 9p issue not still been fixed by upstream? sh-4.1# strace ./wshd --run /share |
Is your plan to use an AF_UNIX socket shared between the host and guest? I can't see that working with two different kernels (host and guest). The guest kernel doesn't know about the kernel objects from the host host. It works with containers because they share the same kernel. Or I am missing something? |
Yes,we use wshd to communicate between guest and host. any other way to replace it? |
This issue got fixed, So close it now |
HI,
I tried to run wshd in clear container, but failed. Did anyone hit this issue before or know any way to workaround it? thanks.
Below was the log:
sh-4.1# strace ./wshd --run /share
execve("./wshd", ["./wshd", "--run", "/share"], [/* 8 vars */]) = 0
uname({sys="Linux", node="1f0511ff4ebce1762a45a656dff21e6f8ba01da5509c5d7c5572dbc9492a684e", ...}) = 0
brk(0) = 0x1eb1000
brk(0x1eb2180) = 0x1eb2180
arch_prctl(ARCH_SET_FS, 0x1eb1860) = 0
brk(0x1ed3180) = 0x1ed3180
brk(0x1ed4000) = 0x1ed4000
stat("/share", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
socket(PF_FILE, SOCK_STREAM, 0) = 3
unlink("/share/wshd.sock") = 0
bind(3, {sa_family=AF_FILE, path="/share/wshd.sock"}, 110) = -1 ENXIO (No such device or address)
dup(2) = 4
fcntl(4, F_GETFL) = 0x8002 (flags O_RDWR|O_LARGEFILE)
fstat(4, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 1), ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fb6f6323000
lseek(4, 0, SEEK_CUR) = -1 ESPIPE (Illegal seek)
write(4, "bind: No such device or address\n", 32bind: No such device or address
) = 32
close(4) = 0
munmap(0x7fb6f6323000, 4096) = 0
brk(0x1ed3000) = 0x1ed3000
exit_group(1) = ?
sh-4.1#
sh-4.1# uname -a
Linux 1f0511ff4ebce1762a45a656dff21e6f8ba01da5509c5d7c5572dbc9492a684e 4.5.0-50.container #1 SMP Mon Oct 24 22:24:01 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
sh-4.1# cat /etc/system-release
CentOS release 6.4 (Final)
sh-4.1#
The text was updated successfully, but these errors were encountered: