Docker Community Forums

Share and learn in the Docker community.

Volumes not mounting after upgrade to Version 17.12.0-ce-win46 (15048)


(Marcelonyc) #1

I upgrade to Version 17.12.0-ce-win46 (15048) earlier today. After the upgrade, none of the containers I start are mounting the volumes I ran them with. Any suggestion about how to debug this?

Here is a inspect sample for one of the containers.

    "Mounts": [
        {
            "Type": "bind",
            "Source": "/c/private",
            "Destination": "/home/private",
            "Mode": "",
            "RW": true,
            "Propagation": "rprivate"
        },
        {
            "Type": "bind",
            "Source": "/c/EBE",
            "Destination": "/EBE",
            "Mode": "",
            "RW": true,
            "Propagation": "rprivate"
        }

I ran a new container and noticed a difference in the definition of the mount. Notice this version has host_mnt prior to source path. The newly created container mapped correctly

“Mounts”: [
{
“Type”: “bind”,
“Source”: “/host_mnt/c/private”,
“Destination”: “/home/private”,
“Mode”: “”,
“RW”: true,
“Propagation”: “rprivate”
}


(Maximzviagintsev) #2

I’m having the same issue. After updating to the latest version and running docker-compose up -d my containers are loaded only partially.
Can’t reach my dev site, WTF?!!


(Klokand) #3

try remove all the unused volume by using ‘docker volume prune’.
It fixed my problem.