Lab 6 - Unable to reach the service externally

joshl

In lab 6, i was able to launch container application but i can not reach it externally. note, i am using an AWS EC2 instance.

:~/labsys/lab6$ sudo docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 779c4a4dbf87 gcr.io/google-samples/gb-frontend:v4 "apache2-foreground" About an hour ago Up About an hour 0.0.0.0:49156->80/tcp, :::49156->80/tcp guestbook 49a6ee4a375a k8s.gcr.io/redis:e2e "redis-server /etc/r…" About an hour ago Up About an hour 0.0.0.0:49155->6379/tcp, :::49155->6379/tcp guestbook-db 6ad849e8a545 wordpress "docker-entrypoint.s…" About an hour ago Up About an hour 0.0.0.0:49154->80/tcp, :::49154->80/tcp wordpress 7bb06b131e21 mariadb "docker-entrypoint.s…" About an hour ago Up About an hour 3306/tcp wordpress-db 3c9ea5b1292b httpd:2.4 "httpd-foreground" 37 hours ago Up 37 hours 80/tcp, 0.0.0.0:49153->8080/tcp, :::49153->8080/tcp apache-cont

when working on these step:
The Guestbook frontend is mapped to port 49156 on the host machine, which points to port 80 on the container. The WordPress frontend is mapped to port 49154 , which maps to port 80 of its own container. Your resulting ports may var y, so moving for ward be sure to select the ports that are shown in your terminal.

In a browser on either the local machine or the host machine, connect to each frontend using http://<VM External IP>:<Wordpress Container Port> and http://<VM External IP>:<Guestbook Container Port> to access WordPress and the Guestbook respectively.

but when i try to reach it thru browser, i get this:

ChristianLacsina964

Which IP address are you trying to use? I was able to replicate the steps on AWS using the external IP (the one I use to SSH) rather than the local IP address.

Also, can you repost the output of your sudo docker ps command in a code block? I think I might see an inconsistency but it's hard to tell from the current formatting.

joshl

here ya go

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
04af3dc3c5b8 gcr.io/google-samples/gb-frontend:v4 "apache2-foreground" About a minute ago Up About a minute 0.0.0.0:49159->80/tcp, :::49159->80/tcp guestbook
6e8a9e591b13 k8s.gcr.io/redis:e2e "redis-server /etc/r…" About a minute ago Up About a minute 0.0.0.0:49158->6379/tcp, :::49158->6379/tcp guestbook-db
ff6cbfaf2200 wordpress "docker-entrypoint.s…" 2 minutes ago Up 2 minutes 0.0.0.0:49157->80/tcp, :::49157->80/tcp wordpress
6dab6b12ac8e mariadb "docker-entrypoint.s…" 3 minutes ago Up 3 minutes 3306/tcp wordpress-db
3c9ea5b1292b httpd:2.4 "httpd-foreground" 47 hours ago Up 47 hours 80/tcp, 0.0.0.0:49153->8080/tcp, :::49153->8080/tcp apache-cont

ChristianLacsina964

In this case your guestbook should be listening at port 49159 and wordpress should be at 49157 on the SSH ip address. Another thing to check would be whether the security group for the AWS machines is allowing traffic to those ports.

When I run it, this is my output:

~$ sudo docker ps
CONTAINER ID   IMAGE                                  COMMAND                  CREATED         STATUS         PORTS                                         NAMES
c628f2505896   gcr.io/google-samples/gb-frontend:v4   "apache2-foreground"     3 minutes ago   Up 3 minutes   0.0.0.0:49155->80/tcp, :::49155->80/tcp       guestbook
d65a7bc8699a   k8s.gcr.io/redis:e2e                   "redis-server /etc/r…"   3 minutes ago   Up 3 minutes   0.0.0.0:49154->6379/tcp, :::49154->6379/tcp   guestbook-db
34270abdc293   wordpress                              "docker-entrypoint.s…"   4 minutes ago   Up 4 minutes   0.0.0.0:49153->80/tcp, :::49153->80/tcp       wordpress
d994e3cac434   mariadb                                "docker-entrypoint.s…"   4 minutes ago   Up 4 minutes   3306/tcp                                      wordpress-db

In my case, my guestbook is available at 49155 and wordpress at 49153. My security group has all of those ports open.

joshl

Do you mind please sharing the AWS SG configs for those ports? I don't need to see your IP, just the SG Configs for those specific ports. My current EC2 does not have an External IP so i had to attach an Elastic IP to it. I configured the instance to one of the port for testing but it didn't work.