Search for a command to run...
Hey, Y'all 👋 Kratik Here :)
Hailing from The City of Lakes, India.
I love to learn and share stuff about DevOps, SRE, Security, Cost Optimization, etc.
Join me on this journey where we will learn together with the help bunch of interesting blogs.
No comments yet. Be the first to comment.
DNS Search Domains, ndots, and Kubernetes Resolver Behavior
Understand how IAM Access Entries can replace aws-auth for managing EKS IAM authentication.
Effective Techniques for Providing IAM Access to EKS Pods
Ever wondered how can you create your own custom Github Action and publish it to the GitHub Marketplace? Let's learn it step by step in this blog.
Let's setup Vault with External-secrets to manage secrets in Kubernetes like never before!
I have assumed that you have some basic knowledge of Docker & Docker Compose!
Dockerfile
docker-compose fileOk So this was some basic info. Now, Let me ask you a question - Have you seen something like this before and ever wondered what it does exactly?
docker-compose -f docker-compose.yml -f docker-compose.prod.yml up -d
By observing the few lines, one can deduce that here we are using two compose files and then launching the compose stack in detach mode(-d)
The basic idea behind this is to keep your main compose file generic for all environments (like dev, stage, and prod) as much as possible.
And for all the needs, which are specific to an environment, pass another file with those configs and it will append all the files to generate the desired config.
Use case example - You are using almost the same config on your environments but for dev, the database port is open for devs to testing OR Suppose if you want to run the dev and stage environment in DEBUG mode but not the prod one!
#1 Usual docker-compose.yml file
web:
image: example/my_web_app:latest
build: .
volumes:
- ".:/code"
ports:
- 8883:80
depends_on:
- db
- cache
db:
image: postgres:latest
command: "-d"
cache:
image: redis:latest
ports:
- 6379:6379
Now, to pass some extra configuration updates, use another compose file called ...
#2 docker-compose-dev.yml
web:
environment:
DEBUG: 'true'
db:
environment:
production: 'true'
ports:
- 5432:5432
Notice in the second override file we only wrote the config we wanted at the respective block of each service.
Now when you want to up your stack, you need to fire the below command :
docker-compose -f docker-compose.yml -f docker-compose-dev.yml up -d
docker-compose.yml and an optional docker-compose.override.yml -f to specify the file name or path.Thanks for reading! have a nice day!
