How can I tell if docker has frozen?

Docker comments like

docker-compose run -d import-external

can take a very long time to run. The one just mentioned has displayed

  • yum install error docker
  • unable to edit /etc/resolv.conf in docker container
  • Filter docker images by name
  • Can't push an image to ECS Private Registry - no basic auth credentials
  • Howto detect in Docker the container kernel version
  • Access Docker features when using Vagrant
  • latest: Pulling from osm2vectortiles/import-external

    and there’s no indication of whether it has frozen or is simply in the middle of a large download. Is there any way to get a progress indicator?

  • How to connect to docker container in local machina [duplicate]
  • How can I grab exposed port from inspecting docker container?
  • Docker app not able to access MySQL running in another container
  • Docker - How to update images
  • bundler: command not found: rails with docker-compose on a sample project
  • Utilizing the --user param to create a user with a Dockerfile container
  • One Solution collect form web for “How can I tell if docker has frozen?”

    The ideal way of starting would be to build the container first and then run the up/run commands. That way the image download happens first with a progress indicator and the up/run without the -d option will show the logs too. If you do need to use the -d option, you can use the docker-compose logs -f command to see the logs.

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