https://hub.imt-atlantique.fr/data-engineering-foundations/technical_environment/index.html Presentation & objectives In a database course, every student needs to run services such as PostgreSQL, MySQL, Redis, ElasticSearch or MongoDB on their own machine. But students use a wide variety of systems—Windows, macOS, Linux, different versions, different configurations—which makes installing and configuring databases a time-consuming and error-prone task. Docker solves this problem by providing isolated, reproducible environments that behave the same on every computer. Instead of struggling with installers, system dependencies, port conflicts, or path issues, students can launch a fully configured database in seconds with a single command. This ensures that everyone works with identical setups, removes “it works on my machine” issues, and lets us focus on learning database concepts rather than debugging local environments. Hugo en-us https://hub.imt-atlantique.fr/data-engineering-foundations/technical_environment/docker_introduction/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://hub.imt-atlantique.fr/data-engineering-foundations/technical_environment/docker_introduction/index.html Docker is a platform that allows applications to run in lightweight, isolated environments called containers. Unlike virtual machines, containers do not include an entire operating system; instead, they rely on Linux kernel features—primarily namespaces and control groups (cgroups)—to provide isolation and resource management. Each container is, at its core, simply a Linux process running on the host, but one that sees its own filesystem, network interface, and process table thanks to namespaces. Meanwhile, cgroups control how much CPU, memory, and I/O the container can use. This combination gives Docker its efficiency and portability: containers start quickly, consume fewer resources, and behave consistently across different environments. https://hub.imt-atlantique.fr/data-engineering-foundations/technical_environment/practical_1/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://hub.imt-atlantique.fr/data-engineering-foundations/technical_environment/practical_1/index.html Duration1h AI Banned Installation First step is obviously to have available the Docker Engine on your computer. Follow the instructions from the installation guide. Testing Starting the Docker Engine results in the service daemon being run. In order to communicate with the service, a client is needed, and during this practical activity, we will mainly use the command line client. We know the temptation to use the graphical Docker Desktop/Dashboard interface will be strong, but writing the complete command instructions to manipulate the different components of your Docker architecture is preferable from a pedagogical point of view. https://hub.imt-atlantique.fr/data-engineering-foundations/technical_environment/practical_2/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://hub.imt-atlantique.fr/data-engineering-foundations/technical_environment/practical_2/index.html Duration1h AI Banned This second practical activity introduces the notions of Dockerfile and Docker compose, two strategies to script the deployment of Docker architecture. Dockerfile A Dockerfile is simply a text file containing a sequence of instructions to build a personalized image. Each line of the Dockerfile starts with a command possibly followed with arguments. A Dockerfile is thus a recipe detailing the different layers of your final image. It starts with a FROM command indicating which base layer to start with.