Further we’ll have a look at a Docker Context and the information it holds to allow us to safely connect to remote Docker engines. We’ll start defining a sample application to use throughout this exercise, then we’ll show how to deploy it on the localhost. The goal of this post is to show how to use contexts to target different environments for deployment and easily switch between them. To address this issue, we rely on Docker Contexts to securely deploy Compose applications across different environments and manage them effortlessly from our localhost. This is not very user friendly and managing deployments of Compose applications across multiple environments becomes a burden. In such cases, the challenge is that docker-compose provided support for running on remote docker engines through the use of the DOCKER_HOST environment variable and -H, –host command line option. From here, we can get the application running locally in a few seconds with a single `docker-compose up` command.Īs developers look to have the same ease-of-deployment in CI pipelines/production environments as in their development environment, we find today docker-compose being used in different ways and beyond its initial scope. All we need to do is write a Compose file containing the configuration for the application’s services and have a running Docker engine for deployment. The docker-compose tool is pretty popular for running dockerized applications in a local development environment.
0 kommentar(er)
