Sponsored by
TechOps Examples
Hey — It's Govardhana MK 👋
Welcome to another technical edition.
Every Tuesday – You’ll receive a free edition with a byte-size use case, remote job opportunities, top news, tools, and articles.
Every Thursday and Saturday – You’ll receive a special edition with a deep dive use case, remote job opportunities and articles.
👋 👋 A big thank you to today's sponsor THE SHIFT
Stop googling AI tools at midnight.
There are over 3,000 of them in The Shift’s vault, already vetted, ready to explore.
Subscribe and get instant access to the tool vault, a 1000+ prompt library, and free AI courses built for people with actual work to do.
Plus, the daily newsletter that keeps you sharp on everything moving in AI in under 5 minutes a day.
They’re also giving away a free 1-year Claude Pro subscription to 3 subscribers.
Subscribe for free to enter. All free. All in one place.
👀 Remote Jobs
Railsware is hiring a Senior DevOps Engineer
Remote Location: Worldwide
Phizenix is hiring a Atlassian Cloud Migration Engineer
Remote Location: Worldwide
📚 Resources
If you’re not a subscriber, here’s what you missed last week.
To receive all the full articles and support TechOps Examples, consider subscribing:
🛠 TOOL OF THE DAY
CLI-Anything - One Command Line: Make any software agent-ready for Pi, OpenClaw, nanobot, Cursor, Claude Code, etc.
🧠 USE CASE
Docker Container Networking With Docker Compose Explained
An entry level DevOps engineer on my team once explained this to me:
“In my docker-compose.yaml, I assign a static IP to a web app container like this:
networks:
custom01:
ipv4_address: x.x.x.xIt works. The app is reachable at a fixed IP, and Nginx can route traffic to it. But the app needs to be built from source. I use a Dockerfile to install packages, build binaries, and set up the environment.
I tried assigning a network inside the Dockerfile, but it didn’t work”. He had hit a common mistake. The Dockerfile and docker-compose.yaml solve different problems.
Dockerfile defines how the image is built. It controls what is inside the container (OS, packages, source code, build steps).
docker-compose.yaml defines how the container is run. It handles ports, volumes, networks, and container relationships.
You cannot attach a container to a network or assign it a specific IP address within a Dockerfile. That configuration is handled at runtime, typically using a docker-compose.yaml file.
The solution
Build the app image using the Dockerfile. Use docker-compose.yaml to run it with proper network settings.
services:
app:
build: ./app
networks:
custom01:
ipv4_address: 192.168.50.10
nginx:
image: nginx:alpine
volumes:
- ./nginx.conf:/etc/nginx/nginx.conf
networks:
custom01:
ipv4_address: 192.168.50.5
networks:
custom01:
external: true
Create the network first:
docker network create --driver=bridge --subnet=192.168.50.0/24 custom01Your Nginx config can then route traffic to http://192.168.50.10.
Takeaway
Use the Dockerfile to define how the image is built.
Use docker-compose.yaml to control how containers run and connect.
Network setup always belongs to the runtime, not the build phase.
🔴 Get my DevOps & Kubernetes ebooks! (free for Premium Club and Personal Tier newsletter subscribers)
Looking to promote your company, product, service, or event to 50,000+ DevOps and Cloud Professionals? Let's work together.
