Trouble with Empty /Workspace

[kbaltrinic]

I am having trouble with the dev environment intermittently where I can vagrant ssh into the box and /workspace is fine (ls /workspace returns what I would expect), but after I run lita-dev and am inside the docker container's env, the /home/lita/workspace folder is empty.

mount | grep workspace shows something like ... /dev/sd9 on /home/lita/workspace ... and ls /dev show no such device.

Exiting the docker environment and running docker restart lita-dev and going back in fixes the problem.

This seems to happen if I leave vagrant up for extended periods, especially on my Mac book Pro which gets paused and resumed all the time as I open and close the lid all day long.

Give I have a workaround, this isn't a big deal but it might be nice if the lita-dev command could identify the situation and restart the container if needed.

[jimmycuadra]

This is likely a problem with the underlying volume management of the VM provider. I've had this type of problem forever with Vagrant VMs.

At this point, it's likely that the whole Lita dev environment will get replaced with a simple Docker/Docker Compose setup. At the time the current VM-based one was built, the "Docker for Mac/Windows" products didn't exist, so the VM was used to provide a (mostly) stable base environment for Docker to run in across host operating systems.