[
https://issues.apache.org/jira/browse/STORM-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16565282#comment-16565282
]
Chris Clarke commented on STORM-1759:
-------------------------------------
In case it's helpful, here's our proxy setup that solves this pretty well:
[https://gist.github.com/xofer/e2a703d80979108c76ce53e5361fbc4d]
There are a handful of links that simply couldn't be rewritten, so remain
broken.
Originally posted on https://issues.apache.org/jira/browse/STORM-580
> Viewing logs from the Storm UI doesn't work in dockerized environment
> ---------------------------------------------------------------------
>
> Key: STORM-1759
> URL: https://issues.apache.org/jira/browse/STORM-1759
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-ui
> Affects Versions: 0.10.0, 1.0.0, 0.9.6
> Reporter: Elisey Zanko
> Priority: Major
>
> I run the Storm using the following docker-compose.yml
> {code}
> version: '2'
> services:
> zookeeper:
> image: jplock/zookeeper:3.4.8
> restart: always
> nimbus:
> image: 31z4/storm:1.0.0
> command: nimbus -c storm.log.dir="/logs" -c
> storm.zookeeper.servers="[\"zookeeper\"]" -c nimbus.host="nimbus"
> depends_on:
> - zookeeper
> restart: always
> ports:
> - 6627:6627
> volumes:
> - logs:/logs
> supervisor:
> image: 31z4/storm:1.0.0
> command: supervisor -c storm.log.dir="/logs" -c
> storm.zookeeper.servers="[\"zookeeper\"]" -c nimbus.host="nimbus"
> depends_on:
> - nimbus
> restart: always
> volumes:
> - logs:/logs
> logviewer:
> image: 31z4/storm:1.0.0
> command: logviewer -c storm.log.dir="/logs"
> restart: always
> ports:
> - 8000:8000
> volumes:
> - logs:/logs
> ui:
> image: 31z4/storm:1.0.0
> command: ui -c storm.log.dir="/logs" -c nimbus.host="nimbus"
> depends_on:
> - nimbus
> - logviewer
> restart: always
> ports:
> - 8080:8080
> volumes:
> - logs:/log
> volumes:
> logs: {}
> {code}
> And opening the logs from the Storm UI doesn't work because all links are
> pointing to different container ids as hosts.
> I guess adding an ability to explicitly specify the logviewer host in the
> storm.yaml would solve the issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
