Hi Running "rbd lock list" inside a Docker container yields mixed results. Sometimes I can get the right results but most times I just get errors. A good run is like this: [root@host server]# docker run --privileged --net=host -v /dev:/dev -v /sys:/sys ceph/base rbd lock list foo --pool kube --id kube -m host:6789 --key=AQAMgXhVwBCeDhAA9nlPaFyfUSatGD4drFWDvQ== 2015-09-09 16:11:16.812858 7f3337ff5840 -1 did not load config file, using default settings. There is 1 exclusive lock on this image. Locker ID Address client.4333 kubelet_lock_magic_host 10.16.154.78:0/1000001 Same commands but with error: [root@host server]# docker run --privileged --net=host -v /dev:/dev -v /sys:/sys ceph/base rbd lock list foo --pool kube --id kube -m host:6789 --key=AQAMgXhVwBCeDhAA9nlPaFyfUSatGD4drFWDvQ== 2015-09-09 16:11:30.430345 7f4159766840 -1 did not load config file, using default settings. 2015-09-09 16:11:30.464193 7f4159766840 -1 librbd::ImageCtx: error finding header: (108) Cannot send after transport endpoint shutdown rbd: error opening image foo: (108) Cannot send after transport endpoint shutdown rbd version: [root@host server]# docker run -ti ceph/base ceph -v ceph version 0.94.2 (5fb85614ca8f354284c713a2f9c610860720bbf3) ceph server version: # ceph -v ceph version 0.80.9 (b5a67f0e1d15385bc0d60a6da6e7fc810bde6047) -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
