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

  • Windows Server 2016 Docker image support for SQL Server?
  • Insert transaction from demo does not work for me (docker kartoza)
  • Securing services within Docker container Using Identity Providers hosted within a container
  • Which Kubernetes component creates a new pod?
  • Trying to install Mezzanine via Docker
  • Why are <none> images created and why doesn't Docker clean them up?
  • 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: MySQL refuses host IP unless I restart it manually
  • Specify location of volumes in docker
  • Jenkins docker agent in declarative pipeline: file not found
  • Docker daemon wont start even after adding user/deleting host environment var etc
  • bash script to start a docker container running a mono console application cannot send commands in interactive mode
  • Sometimes import data Mysql in Docker very slow
  • 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.