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

  • docker mysql connection via php
  • Publishing Docker to AWS from Visual Studio
  • Swarm mode: Inspect worker node's container on manager node
  • I'm unable to connect Docker Remote API using nodejs hosted in AWS
  • Starting oracle with docker: “TNS:listener: all appropriate instances are blocking new connections” error
  • How to change propagation on mounted volumes in docker
  • 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?

  • Docker-compose migrating from links to networking MongoDB database issue
  • Docker-compose error with service env_file
  • Specify the env file docker compose uses
  • How can I increase memory of docker-machine vm from commandline?
  • Run nano server container on a Raspberry PI 3
  • Good strategy for storing data using Docker?
  • 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.