Thanks for all feedbacks. @Mark Miller, @moon soo Lee

I created an umbrella ticker that collects docker image related issues.

- https://issues.apache.org/jira/browse/ZEPPELIN-2667

We might track all problems regarding official images using the ticket.


Thanks.


On Mon, Jun 19, 2017 at 5:27 AM, Mark Miller <mamille...@gmail.com> wrote:

> Thanks, this is working pretty well for me on Ubuntu 16.  I can execute
> all of the spark, python and R code in the tutorial.
>
> I can't run the pig tutorial, but I assume that's because the docker
> container doesn't include a hadoop environment.
>
> I can't run the mahout code either, which surprised me.  I thought the
> "convenience paragraphs" were included to pull any required dependencies.
>
> python: can't open file '../scripts/mahout/add_mahout.py': [Errno 2] No
> such file or directory
>
> python: can't open file 'scripts/mahout/add_mahout_interpreters.py':
> [Errno 2] No such file or directory
>
>
> On Fri, Jun 16, 2017 at 1:22 AM, Park Hoon <1am...@gmail.com> wrote:
>
>> Hi, users.
>>
>> A few months ago the community started to create official docker image
>> for Zeppelin. As of 0.7.2, release process includes building docker image.
>> Thus, every release can ship its own docker image.
>>
>> You can test the docker image for 0.7.2 with this command.
>>
>> *docker run -p 8080:8080 --rm --name zeppelin apache/zeppelin:0.7.2*
>>
>> or you can set docker volume options to persist notebooks and logs like
>>
>> *docker run -p 8080:8080 --rm -v $PWD/logs:/logs -v
>> $PWD/notebook:/notebook -e ZEPPELIN_LOG_DIR='/logs' -e
>> ZEPPELIN_NOTEBOOK_DIR='/notebook' --name zeppelin apache/zeppelin:0.7.2*
>>
>> And here are few links which might be helpful
>>
>> - https://hub.docker.com/r/apache/zeppelin/
>> - https://github.com/apache/zeppelin/blob/master/docs/install/docker.md
>>
>> Since this is an initial version, it might include some bugs or be not
>> easy to configure some options.
>>
>> Hope that we can improve the docker file and deliver flexible images to
>> the community for various environments and use cases.
>>
>> Thanks.
>>
>>
>> FYI, if you are having trouble with access localhost:8080, try to clear
>> browser caches like
>>
>> [image: Inline image 1]
>>
>
>

Reply via email to