Data volumes with Docker on CentOS 6.5 host now working

Trying to mount some data volume from another container failed on CentOS 6.5.

Here are the steps to reproduce:

  • How to upgrade docker container after its image changed
  • Workflow for building, pushing, and testing Docker images inside GKE / Kubernetes
  • level=fatal msg=“ipset [destroy] failed: ipset v6.29: Set cannot be destroyed: it is in use by a kernel component\n: exit status 1”
  • docker, waiting for SSH to be availabe
  • Docker-Squash command not working
  • Symfony 3 with Docker and nginx
  • [me@loco tmp]$ docker run -d --name just-volume -v /foobar busybox:latest echo DONE
    [me@loco tmp]$ docker ps -a
    CONTAINER ID        IMAGE                       COMMAND             CREATED             STATUS                     PORTS               NAMES
    77f58837be52        busybox:buildroot-2014.02   echo DONE           6 seconds ago       Exited (0) 5 seconds ago                       just-volume         
    [me@loco tmp]$ docker run -i -t --volumes-from just-volume busybox:latest /bin/sh
    lxc-start: No such file or directory - failed to mount '/var/lib/docker/vfs/dir/d9a4f2a981ebc2b26f5dd314c2ac14624c4b79de21c32828fce53bbbb7921431' on '/usr/lib64/lxc/rootfs///foobar'
    lxc-start: failed to setup the mount entries for 'd25071e0c976d094709062ee434d1c5d0a5be17c6c35308511bbb46ca718adea'
    lxc-start: failed to setup the container
    lxc-start: invalid sequence number 1. expected 2
    lxc-start: failed to spawn 'd25071e0c976d094709062ee434d1c5d0a5be17c6c35308511bbb46ca718adea'
    lxc-start: The container failed to start.
    lxc-start: Additional information can be obtained by setting the --logfile and --log-priority options.

    The output from various version commands:

    [me@loco tmp]$ uname -a
    Linux loco 2.6.32-431.23.3.el6.x86_64 #1 SMP Thu Jul 31 17:20:51 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
    [me@loco tmp]$ docker version
    Client version: 1.1.2
    Client API version: 1.13
    Go version (client): go1.2.2
    Git commit (client): d84a070/1.1.2
    Server version: 1.1.2
    Server API version: 1.13
    Go version (server): go1.2.2
    Git commit (server): d84a070/1.1.2
    [me@loco tmp]$ docker -D info
    Containers: 2
    Images: 21
    Storage Driver: devicemapper
     Pool Name: docker-8:2-1705787-pool
     Data file: /var/lib/docker/devicemapper/devicemapper/data
     Metadata file: /var/lib/docker/devicemapper/devicemapper/metadata
     Data Space Used: 1504.8 Mb
     Data Space Total: 102400.0 Mb
     Metadata Space Used: 1.7 Mb
     Metadata Space Total: 2048.0 Mb
    Execution Driver: lxc-1.0.5
    Kernel Version: 2.6.32-431.23.3.el6.x86_64
    Debug mode (server): false
    Debug mode (client): true
    Fds: 11
    Goroutines: 10
    EventsListeners: 0
    Init SHA1: 808ba4d09a4b931f5f745154bea886f252a1aef4
    Init Path: /usr/libexec/docker/dockerinit
    Sockets: [unix:///var/run/docker.sock]

    I also reported this as an issue on GitHub:

    Anyone with similar issue or perhaps a solution?

  • MongoDB in Docker - backup database on container shutdown
  • Create your own Docker (sub-)commands
  • Can't connect to mongodb instance running on docker-machine
  • Open/Edit/Save from on the host with app running in container
  • Kubernetes. HTTPS API return `Unauthorized`
  • What is the docker.sock equivalent on Windows 10?
  • Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.