container runs and first log appears but listening on that port is not happening

[samfullman]

In: MacBook using terminal

Hi Steve,
Personally I think you should leave the "Hello World" in place, as that's what guys are going to be searching on and your repo name contains that as well.

Hey I have an issue, I'm able to docker build just fine, but the docker run .. part is not working. "The site cannot be reached". My docker ps -a info:

CONTAINER ID   IMAGE                                 COMMAND                  CREATED         STATUS         PORTS                                                                                                                                  NAMES
0995c28fabed   node-hello-world:latest               "docker-entrypoint.s…"   9 seconds ago   Up 8 seconds   0.0.0.0:8080->8080/tcp                                                                                                                 node-hello-world

trying localhost:8080 and even 0.0.0.0:8080 is just not working.

[stevemar]

Hi @samfullman

Hmm, docker build seem to be working for me...

$ docker build -t node-hello-world:latest .

[+] Building 7.3s (12/12) FINISHED                                                                                      

Same with docker run

$ docker run -it -p 8080:8080 --name node-hello-world node-hello-world:latest
Running on http://0.0.0.0:8080

Opening up a new tab and hitting the URL seems to work too

$ curl http://localhost:8080 
Hello World from IBM Cloud Essentials!

And my docker ps -a is as follows:

$ docker ps -a
CONTAINER ID   IMAGE                                                                                  COMMAND                  CREATED              STATUS                     PORTS                     NAMES
b3271a13d70c   node-hello-world:latest                                                                "docker-entrypoint.s…"   About a minute ago   Up About a minute          0.0.0.0:8080->8080/tcp    node-hello-world

The logs show just a single message that it is up and running too. (use your container ID).

$ docker logs b3271a13d70c
Running on http://0.0.0.0:8080

To me, this sounds like a networking issue. Are you using a VM from another machine by any chance?