nnectionpool._make_request: "GET /v1.36/version HTTP/1.1" 200 568Ĭ_client: docker-compose version 1.21.2, build a133471Ĭ_client: Docker base_url: Ĭ_client: Docker version: Platform = nnectionpool._new_conn: Starting new HTTP connection (1 ): 0.0.0.0 docker-compose.ymlĭ_config_file: Trying paths: ĭ_config_file: No config file found This is the output of running docker-compose -verbose up when running an example Flask application that is part of the Docker best practices project on $ docker-compose -verbose upĬ: Using configuration files.
Search for any images already built for your project.Search for any containers already created for your project.Attempt to inspect or create your project’s volumes.
Attempt to inspect or create your project’s networks.Connect to the configured Docker daemon.Try to load any custom Docker config files.
High level overview of running the up command: You can attach the -verbose flag to any docker-compose command, such as running docker-compose -verbose up to get the full view of what’s happening. Using -verbose to Take a Peek at What’s Happening Without looking at Docker Compose’s source code, it would be reasonable to think that Docker Compose might just parse your docker-compose.yml file and then transform things like services, volumes and networks into various docker commands.Īnd that’s not far from the truth, but Docker Compose isn’t directly calling the docker binary to run these commands.
Docker run image verbose how to#
Updated on June 22nd, 2018 in #docker Docker Tip #60: What Really Happens When You Run docker-compose up? In this tip you'll learn how to look under the hood of what Docker Compose is doing whenever you run any of its commands.
0 kommentar(er)
