Building a CI/CD Pipeline with Jenkins
This lecture covers CI (Continuous Integration) and CD (Continuous Deployment) pipelines, which are one of the four key elements (MSA, CI/CD, DevOps, Container) that make up cloud-native applications. Through this lecture, you can understand and practice the process of building and deploying your own automation pipeline in a local environment and a cloud environment using the CI/CD tool Jenkins.
How to fix error when starting SSH + Docker container on Windows 2
Hello, this is Lee Do-won.
First of all, I would like to thank those who attended the lecture.
This course is one that requires hands-on practice. In particular, we recommend that you install and practice Jenkins, Tomcat, or Docker servers yourself.
Unfortunately, some students (especially Windows students) have written that they are having difficulty setting up the environment required for the practical training. We have not tested all environments, but we have prepared and tested several environments that can be set up, and shared related resources and scripts. We apologize to students who have not been able to resolve the issue.
We have provided a practical guide for Windows + SSH + Dokcer environment through Q&A and additional videos that we shared earlier, but we would like to share some additional information that we have confirmed.
Windows) SSH server (with Docker) execution command (Method 1)
docker run --privileged --name docker-server -itd -p 10022:22 -p 8081:8080 -e container=docker -v /sys/fs/cgroup:/sys/fs/cgroup edowon0623/docker:latest /usr/sbin/init
Windows) SSH server (with Docker) execution command (Method 2, if it does not run with the above command)
docker run -itd --name docker-server -p 10022:22 -e container=docker --tmpfs /run --tmpfs /tmp -v /sys/fs/cgroup:/sys/fs/cgroup:ro -v /var/run/docker.sock:/var/run/docker.sock edowon0623/docker:latest /usr/sbin/init
On some Windows PCs we tested, all of the practical methods below worked normally, but we recently confirmed that there was an error in practical 1 on a Windows PC we purchased (with WSL2 installed). The cause of the error we have currently identified was that the following error occurred during the iptables creation process in WSL2. We looked up various information and tried to solve it, but it did not work properly in the image we created, so we temporarily created an image with the iptables function excluded and tested it. As of now, we have determined that the practical training is possible without any major issues, so we are sharing the image and Dockerfile with you.
https://hub.docker.com/r/edowon0623/docker/tags -> docker pull edowon0623/docker:no_iptables
https://github.com/joneconsulting/docker-files
Therefore, if the Docker server is not started in the Windows environment using the Dind method (Practical Scribe Method 1), try practicing using the command below.
Windows) SSH server (with Docker) execution command (method 3)
docker run --privileged --name docker-server -itd -p 10022:22 -p 8081:8080 -e container=docker -v /sys/fs/cgroup:/sys/fs/cgroup edowon0623/docker:no_iptables /usr/sbin/init
Of course, after starting the Docker container, you must connect via SSH and run the systemctl start docker command to start the Docker server.
Once again, thank you for your interest in the lecture. We will prepare new lectures with better content.
thank you