docker-compose – Türker Yıldırım

Compose profiles, and the service that should have had one

NoteMay 19, 20261 min read

A profile applied to the heavy development services, and one that was missed because it is small. Memory was the criterion for adding a profile and the cost…

The second host, and the failover we finally built

Deep diveMarch 27, 202614 min read

Seven years on one host, and a business requirement that finally arrived. A recovery time that assumes the host comes back.

Docker Compose in production, and why it is still here

Deep diveSeptember 19, 202510 min read

Six years of Compose on a VPS, and an annual conversation about orchestration. Nothing is wrong, which is why the conversation keeps happening.

The compose file that became three compose files

NoteMay 13, 20252 min read

One file with eleven services, of which four run in production, three run locally and four run in both with different settings. The override file being loaded automatically…

A rolling update in twenty lines of shell

NoteJanuary 23, 20251 min read

Compose has no rolling update, and the thing it does not have is twenty lines of shell for a two-replica service. Scaling up, waiting for health, then removing…

Compose v1 reaches end of life, and the alias that hid it

NoteFebruary 21, 20242 min read

A shell alias mapping docker-compose to docker compose, added in 2021, which meant nobody noticed the old binary was still installed and still being used by two scripts.…

A compose profile for the services nobody runs locally

NoteOctober 27, 20232 min read

A stack of eleven services where four are needed by two people occasionally, started by everybody constantly. Memory is the reason: the search pair was 2.4 GB on…

docker compose watch, and the bind mount it replaces

NoteJune 4, 20232 min read

A bind mount of the whole project into the container is the standard local setup and is the reason the stack is slow on some machines. The difference…

A base image we build ourselves, and the CVE report that paid for it

Deep diveMarch 15, 202310 min read

A scanner reporting 41 vulnerabilities, 39 of them in packages we do not use. A weekly report that has never once been actionable.

A compose override file that only exists on one machine

NoteFebruary 22, 20232 min read

docker-compose.override.yml is loaded automatically and is not in version control, which is the point and is also how two developers end up with different stacks. The override file…