Teach Docker-compose - TP1

100%

Teach Docker-compose - TP1

✓ Published0🌍 Public

Last edited Nov 14, 2025

Created on Oct 11, 2018

Three Docker Compose configurations compare ways to manage MySQL data persistence and service networking. The examples use the `version: '2'` Compose API, defining `mysql` and `phpmyadmin` services with environment variables for database credentials and container ports. The first binds a local directory (`./data/db`) as a volume, the second declares a named volume (`mysql-data`) and explicit networks (`mysql-network`), and the third maps a host path (`/data/on/host/dir`). Each file shows YAML structures for `services`, `networks`, and `volumes`, highlighting how Compose handles data lifecycle differences.

AI-generated description

Similar vizzes

Loading thumbnail…

docker compose sample

This example shows a multi-service Docker Compose setup for local development, defining a main application service along with MySQL and Adminer containers. The main service builds from a local context with a development target, mounts the current directory as a volume while preserving the container’s node_modules, exposes port 9229 for debugging, runs `npm run start:dev`, and loads environment variables from a `.env` file. The MySQL service uses the `mysql:latest` image with a native password authentication plugin, sets a root password, and persists data in a named volume. Adminer provides a web-based database client on port 8080, with all services connected via a custom `webnet` network.

66ewis

75% match

Loading thumbnail…

Docker Compose for Omeka-S (forked from https://raw.githubusercontent.com/dodeeric/omeka-s-docker/master/docker-compose.yml) with MySQL

This example visualizes a Docker Compose configuration for running Omeka-S, a web publishing platform, alongside MySQL and phpMyAdmin. The code defines three interconnected services—`mysql`, `pma`, and `omeka`—using the `mysql:latest`, `phpmyadmin/phpmyadmin:latest`, and `dodeeric/omeka-s:latest` images respectively. It shows how named volumes (`mysql`, `omeka`) persist data, while a custom network (`network1`) enables service communication. The YAML file explicitly links the database and admin interface to the Omeka-S container, with port mappings (`80:80` and `8080:80`) exposing the web services.

CCliffordAnderson

72% match

Loading thumbnail…

Config to Run nest and mysql

This example shows a Docker Compose configuration that sets up a NestJS application with a MySQL database and an Adminer interface for database management. The `main` service builds a development container with mounted source code and hot-reloading via `npm run start:dev`, while the `mysql` service uses the official MySQL image with a root password and persistent storage through a named volume. Adminer runs on port 8080 and connects to the MySQL container. The configuration uses Docker Compose’s networking and volume APIs to link services and preserve data across container restarts.

66ewis

70% match

Loading thumbnail…

Example of Dockerfile for teaching

This gallery example presents a collection of Dockerfile and docker-compose configuration snippets for teaching container orchestration. The Dockerfile.php.example demonstrates a multi-step build process using Debian as a base, installing PHP CLI, copying local scripts, downloading remote data, and configuring volumes, ports, and the working directory. The docker-compose files illustrate core Compose features including service definitions with MySQL and WordPress images, port mapping, environment variables, device access, links, and named volumes. The code directly shows YAML syntax for `services`, `volumes`, and specific directives like `build.context`, `depends_on`, and `restart`.

SServuc

69% match

Loading thumbnail…

Example of docker-compose.yml

This example shows a minimal Docker Compose setup that declares two services for a web application. The `docker-compose.yml` file defines a `web` service built from the local directory, which publishes port 5000 to the host, and a `redis` service using the official `redis:alpine` image. The file relies on the Compose specification’s `version`, `services`, `build`, `ports`, and `image` keys, with a YAML structure that maps service names to their configuration. It demonstrates the core pattern of linking an application container to a backing data store without additional network or volume definitions, based on the example from Docker’s official getting-started documentation.

SServuc

65% match

Loading thumbnail…

Gist f575906ce727448e6f3d5f26a151ea55

This example visualizes the network topology defined in a Docker Compose file, showing how the nginx, php, and db services connect through the frontend and backend networks. It renders the service containers as nodes positioned by a force-directed layout from D3’s `d3.forceSimulation`, while edges represent network membership, with each container linked to its respective network based on the YAML configuration. The visualization reads the `docker-compose-network.yml` structure directly, using its service and network definitions to drive the graph’s data model.

SServuc

64% match

Loading thumbnail…

docker-swarm

This example demonstrates a Docker Swarm deployment of a PHP application behind an Nginx load balancer, using a Compose file to define the service topology. The visualization shows the network layer with an overlay network bridging the webapp replicas and the manager-node proxy, while the Nginx configuration references an upstream cluster with multiple server IPs. The PHP container serves a simple script that echoes the container’s hostname and IP, illustrating dynamic scaling behavior. The code relies on Docker Compose’s `deploy` keys for replica counts, update parallelism, and placement constraints.

SServuc

62% match

Loading thumbnail…

Gist 3d7ff1d83fb2177cedceded587ff4aca

This example presents a setup guide for a Docker-based Node.js workshop, illustrating how to launch a project from a Bitbucket-hosted configuration. It shows the command sequence, starting with copying a `docker-compose.yml` file from the provided URL and then running `docker compose up --build` to construct and start the container image. The visualization focuses on the workflow steps, highlighting the use of Docker Compose for service orchestration and image building. The interface displays the copied configuration link alongside the terminal command, making the process explicit for users. No additional data or rendering occurs beyond these instructional elements.

MMistyBlunch

57% match