Inspect docker container FS changes from host

I’ve started a docker container and I’ve modified a file. At some point later I’d like to inspect this change from the docker host. Now I use docker cp to export the file, inspect it, delete it. But this multistep copy-read-delete process seems like over kill if I just want to read a file.

Is there a better way to inspect filesystem changes in a docker container?

  • Mounted docker.sock login not stored
  • Deploying a cluster (i.e. MongoDb / ElasticSearch) with Docker and linking to Java Application
  • For Docker, will apps stop working when host kernel is updated?
  • Why do Docker overlay networks require consensus?
  • Is it practical to deploy an asterisk server using Docker?
  • Golang websocket server on docker container won't send out message to outside world
  • I need more info than docker diff is showing.

  • Docker Compose: Allow images to access host resources (like postgresql)
  • Accessing mysql running in another container by a Jar running in another container
  • go install fail to generate binary
  • How to use Let's Encrypt with Docker container based on the Node.js image
  • How to set WORDPRESS_DB_HOST in docker-compose
  • Docker container UUID
  • 2 Solutions collect form web for “Inspect docker container FS changes from host”

    You can find the filesystem of a running container the Docker data directory, usually /var/lib/docker/. The specific location varies depending on which storage driver is used. In the case of AUFS, the location is `/var/lib/docker/aufs/mnt/${CONTAINER_ID}/.

    $ HELLO_WORLD=$(docker run -d  ubuntu:12.04 /bin/sh -c "while true; do echo Hello world; sleep 1; done")
    $ docker ps
    CONTAINER ID        IMAGE               COMMAND                CREATED             STATUS              PORTS               NAMES
    2524e196adf0        ubuntu:12.04        /bin/sh -c while tru   4 seconds ago       Up 3     seconds                            naughty_brown
    $ echo $HELLO_WORLD
    $ sudo ls /var/lib/docker/aufs/mnt/${HELLO_WORLD}/
    bin  boot  dev  etc  home  lib  lib64  media  mnt  opt  proc  root  run  sbin  selinux  srv  sys  tmp  usr  var

    This is not a general solution, but in special cases, you can use mounted volumes:

    Start the container with volume:

    sudo docker run -v /host_path/shared:/shared <container>

    Store files you want to inspect in container dir /shared or copy & ln files to /shared and make needed files symbolic links to files stored in /shared.

    cp /mydir/myfile /shared/myfile
    ln -s -f /shared/myfile /mydir/myfile

    Then you can inspect these files directly in /host_path/shared.

    Note: You cannot symbolic-link special files like /etc/passwd, /etc/hostname etc.

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