Uploaded image for project: 'Product Technical Learning'
  1. Product Technical Learning
  2. PTL-8439

DO280-419: Able to access a web container (on Workstation) from node1 or node2 directly without port-forwarding

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Can't Do
    • Icon: Major Major
    • None
    • DO280 - OCP 3.9 1 20180828
    • DO280
    • ILT
      ROL/VT

    • ILT
    • en-US (English)

      URL:
      Reporter RHNID: adrianling
      Section: -
      Language: en-US (English)
      Workaround: Just talk about the Docker Network architecture, don't do the demo, i.e. trying to access the container from node1.

      Alternatively, install docker on node1, and then try to access the container from node2 - this will fail as it should.

        • note: once OCP has been setup, this bug went away - I can no longer access the container running on Workstation from node1

      Description: This is for DO285 (not DO280).

      Ch3 - Accessing Docker Networks. (pg 68 of DO285 Student Guide).

      Workstation: docker run -d --name=web httpd

      docker inspect web | grep IPAddr --> 172.17.0.2

      Login to 'node1'

      node1: ~$ curl http://172.17.0.2 <-- I get a response from the 'web' container running on Workstation.

      This shouldn't happen right?

      Docker isn't running on node1 (and this is before setting up the OCP 3.9 cluster)
      (this bug shows up in VT labs as well)

            jimrigsbee_jira Jim Rigsbee (Inactive)
            adrianling Adrian Ling (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: