Julio Montes

this is a very known issue with 9p, @vinay-y could you try with devicemapper? docker: https://docs.docker.com/engine/userguide/storagedriver/device-mapper-driver/#configure-docker-with-the-devicemapper-storage-driver

@jovizhangwei could you please add more information? for example the container you are using and the command used to start the container

@mcastelino that's correct

using runc as runtime I can't reproduce the issue ``` $ mount | grep "docker" /dev/mapper/fedora-root on /var/lib/docker/overlay type xfs (rw,relatime,attr2,inode64,noquota) ```

@grahamwhaley yes, qemu is still running ``` $ ps -ef | grep qemu root 6859 1 1 08:45 ? 00:00:13 /usr/bin/qemu-lite-system-x86_64 -name pod-659ed2faab0b010430e3d23ef4ca1827e28f47a13e5f9664b90f014a8eaeed66 -uuid 36353965-6432-6661-6162-306230313034 -machine pc,accel=kvm,kernel_irqchip,............ ``` ``` $...

I can't reproduce this issue # Meta details Running `cc-collect-data.sh` version `3.0.12 (commit 8311a66949584c617fcbed972a1146c275c64e00)` at `2017-12-22.08:13:41.751395188-0600`. --- Runtime is `/bin/cc-runtime`. # `cc-env` Output of "`/bin/cc-runtime cc-env`": ``` [Meta] Version =...

this issue was fixed in qemu 2.10 (last time I tested) :)

thanks @erick0z for the analysis, and yes, definitely a patch in containerd and docker is needed

seems like part of the issue was introduced in the revision e1cc3cb69a0738bb678a208750577fdd5296c577, checking out 1 commit before that revision the container runs, but the device is not hot plugged ```shchecking...

@amshinde no, it doesn't work