[
https://issues.apache.org/jira/browse/ZEPPELIN-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14392837#comment-14392837
]
RJ Nowling commented on ZEPPELIN-10:
------------------------------------
[~bzz] I think that Zeppelin's usage of 2 ports causes multiple problems with
port forwarding. [~epakhomov]'s use case (wanting to be able to use random
ports) is one example of this being a problem. If Zeppelin is ever deployed on
kubernetes, the port-forwarding issues will be a huge stumbling block. Another
is related to authentication using a reverse proxy such as nginx.
I suggest we either change the JIRA to document the port-forwarding issues or
create a new JIRA.
> Zeppelin doesn't compatible with docker.
> ----------------------------------------
>
> Key: ZEPPELIN-10
> URL: https://issues.apache.org/jira/browse/ZEPPELIN-10
> Project: Zeppelin
> Issue Type: Improvement
> Components: GUI
> Affects Versions: 0.5.0
> Reporter: Egor Pakhomov
> Priority: Minor
>
> Zeppelin put UI on ZEPPELIN_PORT and web_socket on ZEPPELIN_PORT+1. When you
> run docker with standart -P
> argument(https://docs.docker.com/userguide/usingdocker/) it maps these ports
> to some other ports. For example you set ZEPPELIN_PORT=8080 and export 8080,
> 8081. But in reality it would be some other ports(49159, 49160). And Zeppelin
> don't know anything about them. And UI doesn't work properly.
> Please see https://github.com/epahomov/docker-zeppelin
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
