Uploaded image for project: 'Hawkular'
  1. Hawkular
  2. HAWKULAR-1047

hawkular-aio doesn't work out of the box with Docker Tools

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Major Major
    • None
    • 1.0.0.Alpha 9
    • _am_uncertain
    • None
    • Hide
      1. Create default Docker image using Docker Manager
      2. Run docker run -d -p 8080:8080 jboss/hawkular-aio as per the Quickstart instructions,
      3. Connect to Hawkular via browser using VM IP (e.g. http://192.168.99.100:8080)

      The browser will be redirected to: http://localhost:8080/auth. I've been able to work round it by launching via the following: 

      docker run -d -p 8080:8080 jboss/hawkular-aio /opt/jboss/hawkular/bin/standalone.sh -b 0.0.0.0 -bmanagement
0.0.0.0 -Dkeycloak.server.url=http://192.168.99.100:8080/auth
      Show
      Create default Docker image using Docker Manager Run docker run -d -p 8080:8080 jboss/hawkular-aio as per the Quickstart instructions, Connect to Hawkular via browser using VM IP (e.g. http://192.168.99.100:8080 ) The browser will be redirected to: http://localhost:8080/auth . I've been able to work round it by launching via the following: docker run -d -p 8080:8080 jboss/hawkular-aio /opt/jboss/hawkular/bin/standalone.sh -b 0.0.0.0 -bmanagement 0.0.0.0 -Dkeycloak.server.url=http: //192.168.99.100:8080/auth

      When connecting to Hawkular after installing via Quickstart Docker instructions into a Docker Tools installation on Windows the KeyCloak URI is not correct by default and results in being directed to 'http://localhost:8080/auth' which unfortunately resolves to the Windows instance and not the VM.

              Unassigned Unassigned
              dansiviter Daniel Siviter (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: