Andreas Eberle created ZEPPELIN-5200:
Summary: Docker Images not working
Key: ZEPPELIN-5200
URL: https://issues.apache.org/jira/browse/ZEPPELIN-5200
Project: Zeppelin
Issue Type: Bug
latest one.
> > Thank you for moving it forward!
> >
> >
> > On Wed, Jul 29, 2020 at 1:11 PM Philipp Dallig >
> > wrote:
> >
> > > Hi Zeppelin developer,
> > >
> > > I would like to move forward the provision of docker images for
t; wrote:
>
> > Hi Zeppelin developer,
> >
> > I would like to move forward the provision of docker images for
> Kubernetes.
> >
> > Right now we have three open PR:
> >
> > - https://github.com/apache/zeppelin/pull/3380
> > - https://github.c
Hi Philipp
That would be nice to do finally :-)
from my side I'm ok with having only the latest one.
Thank you for moving it forward!
On Wed, Jul 29, 2020 at 1:11 PM Philipp Dallig
wrote:
> Hi Zeppelin developer,
>
> I would like to move forward the provision of docker images for K
Hi Zeppelin developer,
I would like to move forward the provision of docker images for Kubernetes.
Right now we have three open PR:
- https://github.com/apache/zeppelin/pull/3380
- https://github.com/apache/zeppelin/pull/3769
- https://github.com/apache/zeppelin/pull/3859
I would like
Hi all
I see on https://hub.docker.com/r/apache/zeppelin/tags that latest images
are tagged as apache/zeppelin:0.9.0 - shouldn't we try to fix the tags to
say that it's 0.9.0-preview1?
--
With best wishes,Alex Ott
http://alexott.net/
Twitter: alexott_en (English), alexott
Hoon Park created ZEPPELIN-2937:
---
Summary: Allow build RC docker images
Key: ZEPPELIN-2937
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2937
Project: Zeppelin
Issue Type: Test
Hoon Park created ZEPPELIN-2667:
---
Summary: [Umbrella] Improving Official Docker Images
Key: ZEPPELIN-2667
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2667
Project: Zeppelin
Issue Type
Github user 1ambda closed the pull request at:
https://github.com/apache/zeppelin/pull/1761
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1761
#2264 was merged.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so,
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1761
Let me create new PR which including only 1 OS (ubuntu) based on this PR.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Guys,
coukd somebody from fellow PMCs, who is currently working on subj chime in
to https://issues.apache.org/jira/browse/INFRA-12781 and comment on Bintray
access/image publishing?
I'm out of capacity to do that right now but still think it would be cool
to have Docker images for each release
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1761
@felixcheung Thanks for review.
Previously, we discussed about separating images in
[ZEPPEILN-1711](https://issues.apache.org/jira/browse/ZEPPELIN-1711)
IMO, having 1 image which
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1761
@1ambda ping
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1761
My apologies if discussed before, but is there a reason for separating into
Scala, Python, R individual Docker images? Don't people want to run Python and
R together, for example
Github user mfelgamal commented on the issue:
https://github.com/apache/zeppelin/pull/1761
@1ambda awesome!.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1538
First and second failing CI profile hit
[ZEPPELIN-1797](https://issues.apache.org/jira/browse/ZEPPELIN-1797)
Spark 1.5 had another troubles \w `DepInterpreterTest`
```
16/12/13
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1538
Looks great to me, thank you @1ambda @mfelgamal
Let's wait for CI results and merge to master, if nothing comes up and
there is no further discussion!
---
If your project is set up for it,
Github user mfelgamal commented on the issue:
https://github.com/apache/zeppelin/pull/1538
@1ambda that sounds awesome job, thank you very much. Now the PR is merged.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1538
@mfelgamal
I agree with you opinion. We can directly use `usr/local/zeppelin` instead
of `start-zeppelin.sh`.
I'v just created PR for removing `start-zeppelin.sh` related files,
GitHub user mfelgamal reopened a pull request:
https://github.com/apache/zeppelin/pull/1538
[ZEPPELIN-1386] Docker images for running Apache Zeppelin releases
### What is this PR for?
This PR is for making docker images for zeppelin releases. It contains a
script
Github user mfelgamal closed the pull request at:
https://github.com/apache/zeppelin/pull/1538
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user mfelgamal commented on the issue:
https://github.com/apache/zeppelin/pull/1538
@bzz @1ambda are there further discussion?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user mfelgamal commented on the issue:
https://github.com/apache/zeppelin/pull/1538
@bzz @1ambda the script `start-zeppelin.sh` isn't important, it just
enforce using port `8080` and zeppelin home dir `/usr/local/zeppelin`, we can
ignore it and use `zeppelin.sh`.
---
If your
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1538
@mfelgamal could you please explain, why do you think one more script is
needed - `start-zeppelin.sh` and why `CMD["/bin/zeppelin.sh"]` can not be used
as entrypoint for the image?
@1ambda
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1538
@mfelgamal The reason, we can't run zeppelin binary on this docker image is
because of **dumb-init**. It prevent from running zeppelin well by just
installing **dumb-init**.
---
If your project
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1538
@mfelgamal that sounds awesome job, thank you very much.
Please let me test it tomorrow and get back to you here, but otherwise I
think it's ready to be merged!
---
If your project is set
Github user mfelgamal commented on the issue:
https://github.com/apache/zeppelin/pull/1538
@bzz I removed `curl build-base make gcc g++` for decreasing the image
size, now it's `301 MB`.
And `R` is run well.
---
If your project is set up for it, you can reply to this email and
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1538
Sort of. There's Conda for R:
https://www.continuum.io/content/preliminary-support-r-conda
But generally some R package are compiled on installation; knitr is a
relatively bigger one.
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1538
@mfelgamal yes, exactly. Do you think this is possible? I wonder if the
image size would go down, if we remove those guys after getting `knitr`.
The goal would be to have a _minimal_ image that
Github user mfelgamal commented on the issue:
https://github.com/apache/zeppelin/pull/1538
@bzz I think that we need to install `build-base make gcc g++` to build
`knitr` package in R. And I wonder if we could remove them after building
`knitr`. Is this right?
---
If your project
Hoon Park created ZEPPELIN-1711:
---
Summary: Create runnable zeppein docker images per released version
Key: ZEPPELIN-1711
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1711
Project: Zeppelin
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1538
Now this issue is like more about building base image :) I will start
working on a new JIRA issue as @bzz mentioned about creating runnable zeppelin
images per version based on this. That would be
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1538
to recap - theare are two final things, that would be very nice to have in
this image:
- find a way to reduce base image size from ~500mb i.e by installing R
without `build-base make gcc g++`
386] Docker images for running Apache Zeppelin releases `. It can
be done later i.e by setting up CI automation that runs nightly build \w
something similar to `create_release.sh`. Important thing there would be to
make sure that's clearly marked as non-release, but just as a developer's
artef
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1538
@mfelgamal @bzz
I think we should dockerize binary zeppelin images first because more users
use binary versions.
---
If your project is set up for it, you can reply to this email and
Github user mfelgamal commented on the issue:
https://github.com/apache/zeppelin/pull/1538
Hi @bzz
So far, we have binary versions from 0.5.0 to 0.6.2, which help us building
docker image to each version instead of building the source code, but I mean
that if you want to
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1538
Great job @mfelgamal !
The idea was to try to avoid building separate artefacts for Docker and use
official convenience binaries from Apache release.
Am I mimssing something, or
Github user mfelgamal commented on the issue:
https://github.com/apache/zeppelin/pull/1538
@1ambda It's good if we did that in apache zeppelin repo. but in this case
instead of using the created binary versions, we should build the source code
inside the docker.
Like that:
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1538
@mfelgamal
Hi :) ping
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
docker images in your
repository https://github.com/mfelgamal/zeppelin-dockers **But not this PR**
So I am asking, what about adding `Dockerfile`s which can be automatically
built into the https://github.com/apache/zeppelin repository like you did in
your own.
After that, we can create
Github user mfelgamal commented on the issue:
https://github.com/apache/zeppelin/pull/1538
@astroshim @bzz @1ambda
* Now I added a start-zeppelin.script to zeppelin-base image. It allow user
to modify some configs by passing env variables. Also the user can share the
logs and
Github user mfelgamal commented on the issue:
https://github.com/apache/zeppelin/pull/1538
@1ambda I already use automated build of dockerhub, when push any new
commit to my repo on github, the dockerhub builds the images recently. For
point 2, It's good point and I will take a look
Github user mfelgamal commented on the issue:
https://github.com/apache/zeppelin/pull/1538
@1ambda Thank you for your review, The issue is solved, you can check
again. And Thank you for the suggested enhancement for zeppelin.sh script, I
think it will make the image better
---
If
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1538
Additionally, It would be better to
- run zeppelin immediately (using `zeppelin.sh` because we can run docker
as daemon mode)
- allow user to modify config important config files by
Github user mfelgamal commented on the issue:
https://github.com/apache/zeppelin/pull/1538
@astroshim I think it is just a message and the shell run normally. you can
run with this command `docker run --rm -it -p 8080:8080 -p 8081:8081
mahmoudelgamal/zeppelin-release:0.5.0 -c bash`.
Github user mfelgamal commented on the issue:
https://github.com/apache/zeppelin/pull/1538
@astroshim R and Python are installed and I think that the tutorials should
be run without errors.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user astroshim commented on the issue:
https://github.com/apache/zeppelin/pull/1538
@mfelgamal Ping.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1538
@mfelgamal Awesome!
There are some places to inform the page's existence to the users.
Please check [documentation
Github user khalidhuseynov commented on the issue:
https://github.com/apache/zeppelin/pull/1538
@mfelgamal first of all thanks for initiative on this one, and few points
here:
* as i can see here Zeppelin images will be with hardcoded
`$ZEPPELIN_HOME/conf` folder and in order
Github user astroshim commented on the issue:
https://github.com/apache/zeppelin/pull/1538
@mfelgamal I checked point 1 and 3. Thank you fix properly.
Could you also fix to run the `R Tutorial` and `Python Tutorial` too?
I think all tutorial should be ran without error.
Github user mfelgamal commented on the issue:
https://github.com/apache/zeppelin/pull/1538
@astroshim Thank you for your reviews, Can you check the docker image again?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user astroshim commented on the issue:
https://github.com/apache/zeppelin/pull/1538
@mfelgamal Thank you for contributing this.
I have several questions.
1. I think it needs `-it` option for running docker.
so The command to run zeppelin docker should be
Github user mfelgamal commented on the issue:
https://github.com/apache/zeppelin/pull/1538
@bzz Thank you for your feedback. A MD documentation page is added to the
install section of Zeppelin documentation.
---
If your project is set up for it, you can reply to this email and have
54 matches
Mail list logo
