docker-compose where can I get a detail log (info) about what happened

I’m trying to pull and set a container with an database (mysql) with the following command:

docker-compose up

But for some reason is failing to start the container is showing me this:

  • Getting all open connections within a docker image
  • How do I migrate my current deployment methodology to one using Docker?
  • How can I connect celery container to rabbitmq container when using --net=host?
  • Error running nodemon in Docker
  • Jenkins and docker-compose
  • Dockerfile for NGINX Web server
  • some_db exited with code 0

    But that doesn’t give me any information of why that happened so I can fix it, so how can I see the details of that error?.

  • Is it possible to create ipv4-enabled Docker Machine on Windows 10?
  • How to run docker containers on different machines
  • Running Mkbootstrap for DBI () => DBIXS.h:22:20: fatal error: EXTERN.h: No such file or directory
  • Docker - A clean tomcat image
  • cf ic plugin not able to find docker daemon while authentication
  • Docker: how to work with local files?
  • 2 Solutions collect form web for “docker-compose where can I get a detail log (info) about what happened”

    Instead of looking for how to find an error in your composition, you should change your process. With docker it is easy to fall into using all of the lovely tools to make things work seamlessly together, but this sounds like an individual container issue, not an issue with docker compse. You should try building an empty container with the baseimage you want then using docker exec -it <somecontainername> sh to go into it and run the commands you’re trying to execute in your entrypoint manually to find the specific breakpoint.

    Try at least docker logs <exited_container_name/id> (or more recently: docker container logs <exited_container_name/id>)

    That way, you can check if there was any error message.

    An exited container means the main process stopped: you need to make sure that main process remains up in order for the container to not exit immediately.

    Try also docker inspect <exited_container_name/id> (or, again, docker container inspect <exited_container_name/id>)
    If you see for instance "OOMKilled": true, that would mean the container memory was exceeded. You can also look for the "ExitCode" for clues.

    See more at “Ten tips for debugging Docker containers” from Mark Betz.

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