-
Notifications
You must be signed in to change notification settings - Fork 95
Container stuck in starting after mounting vsphere volume the second time #2083
Comments
@danielbjornadal. was able to run this test with docker CE 18.03.0 and unable to repro the issue. But from your logs looks like the plugin is able to report the status of the volume accurately (attached/detached). Suggest opening an issue on Docker as this doesn't seem to be a plugin issue. |
@govint. We upgraded to 18.03.0-ce, and the issue still persist.
Is there any debugging we could try on the ESXi host? |
@danielbjornadal, is this the problem, docker ps -a docker exec -it b8c51d612bd7 bash docker exec -it b8c51d612bd7 /bin/bash / # ps bash doesn't exist in the busybox image |
@govint My bad. I was so focused on the problem, I did not check that busybox had bash. The problem started with using this plugin through Rancher. If I then try to to bash into the container from the host, it works.
Rancher Server: v1.6.17-rc3 |
@danielbjornadal ok, without Rancher this problem doesn;t seem to be an issue. Could you check with Rancher on this issue first. If on Rancher the plugin shows the proper status attached/detached at least we know the plugin is mounting/unmounting the volume whenever it's requested to do so. I don't believe this is a plugin issue. |
Rancher issue: rancher/rancher#12863 |
Intro
After creating a vsphere volume, and mounting it to a container for the second time, the container is stuck in starting state.
Versions
ESXi VIB Driver: 0.21.2
Container stuck in starting state
# docker run -d -t --name voltest --volume-driver vsphere -v [email protected]:/mnt busybox
Container stopped
The text was updated successfully, but these errors were encountered: