Joey777210

大佬，另外发现使用HTTP对持久节点健康检查时，naming-server.log中打印大量的`Client change for service .......` 和 `http check started before last one finished`日志，节点大量不健康，请问可能的原因是什么呢？ @KomachiSion

Client change for service发生的频率非常高，毫秒级地在刷新日志； 探活频率的问题我通过改代码的方式暂时解决了

hello there! I dont know if you guys have fix that problem yet... I got the same error while writing my own container...

您好，@dadahua555 ,我也是在ubuntu18.04上运行代码，遇到了run -d top时后台并没有top的情况，请问您是否有遇到？

同样是pivot_root这里，我加入了这个方法之后，在busybox中，所有的mount点和PID都没有了 控制台 time="2020-02-23T23:02:56-08:00" level=info msg="args: [/tmp/___go_build_Socker run -ti sh]" {"level":"info","msg":"command init write is sh","time":"2020-02-23T23:02:56-08:00"} {"level":"info","msg":"socker: exit container","time":"2020-02-23T23:02:56-08:00"} {"level":"info","msg":"init come on","time":"2020-02-23T23:02:56-08:00"} {"level":"info","msg":"command in init is [sh]","time":"2020-02-23T23:02:56-08:00"} {"level":"info","msg":"Current location is /home/joey/go/busybox","time":"2020-02-23T23:02:56-08:00"} {"level":"error","msg":"mount2...

同时，如果我在进入busybox容器中后，使用命令 `mount -t proc proc /proc` 进行手动mount，会提示我没有权限