igakp.blogg.se

Oh right, the Docker daemon needed to be running: sudo systemctl start docker I tried running a simple container: sudo docker run -rm -it -public 8080:80 alpine shĭocker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Restart iptables: sudo systemctl restart iptables

Follow steps to install Docker on CentOS:Ĭhange the FORWARD chain policy to DROP in /etc/sysconfig/iptables: :FORWARD DROP.In my test I am going to run a mock HTTP server using netcat, so I opened port 8080 to the world in the AWS security group for these EC2 instances.Īfter launching the EC2 instance, I ran through the following steps to configure the host: To test the differences, I used Amazon AWS EC2 t2.nano instances based on the CentOS 7 (x86_64) – with Updates HVM AMI. Below I will demonstrate some of the differences between Docker and Podman in terms of iptables changes, and provide a workaround for Podman. I ran into some unexpected problems publishing ports with Podman, which had to do with my default DROP policy on the iptables FORWARD chain. I have recently been learning about podman, a tool for running containers that has a command syntax that matches Docker, but that does not require a Docker daemon and which does not require root privileges.