Hello everyone! I'm excited to share with you the project I completed to enhance my system administration skills using Docker. I created a small infrastructure composed of various services that follow specific rules, and worked in a virtual machine using docker-compose to complete the project.
With Docker, I could run each service in a dedicated container, making it easier to manage and isolate them. I used Dockerfiles to build the containers, with each Docker image having the same name as its corresponding service. My Makefile called these Dockerfiles in the docker-compose.yml file, making it easy to build the Docker images.
Docker provides a lightweight alternative to traditional virtual machines, making it highly portable and easy to move between environments. Docker also takes care of managing the underlying infrastructure, so I didn't have to worry about it.
To ensure security, I made sure there were no passwords in my Dockerfiles and used environment variables to configure the services. I stored these environment variables in a .env file for better organization.
Overall, this project was an excellent opportunity to learn about Docker's benefits and gain hands-on experience in creating a small infrastructure.
In this section, I will describe the various Docker containers that I have set up for my infrastructure. These containers include NGINX with TLSv1.3, WordPress with php-fpm, MariaDB, Adminer, an FTP server connected to the WordPress volume, a static website container, and three containers for visualizing all of the containers status in Grafana. To connect these containers, I have established a docker-network.
The NGINX container is configured to support only TLSv1.3, which ensures secure communication between clients and the server.
The WordPress container includes php-fpm, which is installed and configured. It does not include NGINX, as I have set up a separate container (the previous one) for this purpose.
The MariaDB container provides a database management system for the WordPress website.
To store the WordPress database, I have set up a volume that is mounted to the MariaDB container.
I have also set up a second volume that contains the WordPress website files.
In addition to these containers, I have set up an Adminer container, which provides a web-based interface for managing the MariaDB database.
To connect the FTP server to the WordPress volume, I have bind-mounted the volume to the FTP container.
I have also set up a static website container, which serves as an example of how to run a containerized website that does not require a dynamic content management system like WordPress.
To monitor the performance of the infrastructure, I have set up three containers for visualizing the data in Grafana. These containers receive data from InfluxDB, which is responsible for storing the performance metrics of the infrastructure. To gather this data, I have set up another container called Telegraf, which gets the container usage data from the docker.sock file.
Finally, to connect all of these containers, I have established a docker-network, which allows them to communicate with each other securely and efficiently.
To get started with this project, follow these steps:
- Clone the repository to your local machine:
git clone https://github.com/soofiane262/Inception.git- Navigate to the project directory:
cd Inception- Create the necessary volumes for the project, build the Docker images and start the Docker containers:
make- To stop the containers, run the following command:
make downTo run the Docker containers, use the following command:
makeThis command will create and start all the containers defined in the srcs/docker-compose.yml file.
To view the containers, run the following command:
make psThis command will display the status of all the containers defined in the srcs/docker-compose.yml file.
To stop the containers, run the following command:
make downThis command will stop all the containers defined in the srcs/docker-compose.yml file.
make fcleanThis command will stop and remove all the containers defined in the srcs/docker-compose.yml file, and remove the volumes created by the project.
To restart the containers, run the following command:
make reThis command will remove the volumes, rebuild the containers, and start the containers again.
- Docker
- Dockerfile
- Dockerfile best practices
- Nginx
- OpenSSL
- Bash
- WordPress CLI
- MariaDB
- Adminer
- Telegraf
- InfluxDB
- Grafana
The Inception project was created by Soufiane El Marsi as part of the common core's curriculum for the 1337 Coding School's System Administration and Networking branches, a coding school located in Morocco, Africa, that is a member of the renowned 42 Network of coding schools. The school is also powered by the Mohammed VI Polytechnic University (UM6P), which provides world-class resources and expertise to its students.
As a member of the 42 Network, 1337 Coding School follows the same innovative and immersive educational model, which is based on project-based learning and peer-to-peer collaboration. This means that students are free to learn at their own pace, and are encouraged to work on real-world projects that challenge and inspire them.
The school's partnership with UM6P ensures that students have access to the latest technologies and tools, as well as world-class faculty members and experts in the field of computer science. This allows students to gain a comprehensive understanding of coding and computer science, while also developing the practical skills needed to succeed in the tech industry.
Overall, 1337 Coding School is a unique and innovative institution that provides an exceptional education in coding and computer science, while also preparing students for success in the rapidly-evolving tech industry.
Contributions to this project are welcome. To contribute, please follow these steps:
- Fork the project repository.
- Create a new branch for your feature or bug fix.
- Make your changes and commit them with descriptive commit messages.
- Push your changes to your forked repository.
- Create a pull request to the original repository.
This project is licensed under the MIT License - see the LICENSE file for details.