I build and debug containers most weeks, usually at the worst time. These eight tools write the boring files for me, check the ones I wrote by hand, and tell me plainly when a port or a volume will collide before I find out from a failed deploy.
Add your services one at a time and get a compose file you can save as docker-compose.yml and run with docker compose up.
Tip: host ports must be unique across services, or the second container will fail to start. I check that for you when you generate.
Fill in the pieces of a container image and get a Dockerfile back. I use this when I am starting a new service and do not want to type the same five lines from memory.
Paste a Dockerfile and I count its layers, estimate the size of each one, and flag the habits that bloat images. Sizes are rough estimates from common base images and commands, not a real build, so treat them as a guide.
Paste a Dockerfile and I check it against the rules I have learned the hard way: pin your tags, clean up after apt-get, do not run as root, COPY beats ADD. Each finding names the line it came from.
Paste any container image reference and I split it into registry, namespace, image, tag, and digest, and show what the defaults are. Handy when a deploy fails and you are not sure which registry it actually pulled from.
Paste a compose file and I check the structure: every service needs an image or a build, ports need the host:container shape, depends_on must point at real services. This handles common YAML; it is not a full parser, so odd YAML may still slip past.
List your host to container paths, one per line, and I turn them into docker run -v flags and a compose volumes block. Named volumes and bind mounts both work.
A host path starting with ./ or / is a bind mount. A plain name like logs is a named volume Docker manages for you.
List your host to container ports, one per line, and I draw the map and flag the collisions. Two services on the same host port is the classic one, and it always shows up at 2 AM.