Docker images on different docker versions

I have a docker installation of version 1.12.0 on my development server.

I would like to test my image on a different server (testing) that is a replica of the production environment.

  • How to get docker-compose to always re-create containers from fresh images?
  • Docker container networks
  • W: Size of file /var/lib/apt/lists/http.debian.net_debian_dists_jessie_main_binary-amd64_Packages.gz is not what the server reported 9101219 9117278
  • Symfony 2 application on Vagrant + Docker
  • Network connection inside a container
  • Curl in Docker entrypoint script
  • The highest version of Docker I could install is 1.7.0.

    To move the image I use the commands:

    $ docker save -o my-image-file.tar my-image

    And to import on the test server:

    $ docker load -i my-image-file.tar

    And worked as I had:

    $ docker images
    REPOSITORY          TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
    my-image      0.0.1-alpha.0       4f73652ffdd1        12 days ago         813.4 MB

    But when I try to run it, I got the following issue:

    $ docker run --rm -t my-image:0.0.1-alpha.0

    Error response from daemon: Cannot start container 1388707e60edd19170f3064c548da7bf72f045a85498854339e3447c2ab97e98: device or resource busy

    If I run the docker ps:

    $ docker ps
    CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES


    $ docker ps -a
    CONTAINER ID        IMAGE                          COMMAND             CREATED             STATUS              PORTS               NAMES
    d96a19b4dcc0        my-image:0.0.1-alpha.0   "npm start"         6 seconds ago                                               focused_goldstine

    Is this an issue between the 2 different docker versions?

    Can I fix it without use the same docker version?


    I set up the internet connection and try to launch a container downloaded from the registry.

    It pull the image, but cannot run the container.

    Same error.

  • Docker build error on Mac OS X
  • java tomcat let's encrypt with docker
  • Pandoc HTML to DOCX images load locally but not on server
  • Serving react app with NGINX on /admin instead of / loads files but does not render application
  • Can't connect to mysql container from localhost
  • Running multi-node kubernetes using docker
  • One Solution collect form web for “Docker images on different docker versions”

    1.7 is a pretty old version. In 1.8.3 there was a security patch that made some changes. You can read about it in the Docker blog. You may be just using incompatible versions.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.