Add Dockerfile about apache-spark-node

[tobilg]

I can take care of this. Any preference concerning the distribution?

[henridf]

That would be great!

I'm unexperienced when it comes to dockerfiles, but my guess would be to start off from an existing spark or node dockerfile, which means going with whatever distribution that is using (likely standard ubuntu).

Does this make sense?

[tobilg]

Afaik there's no official Spark image. As it has more dependencies than Node, I'd suggest to start with a Java/Ubuntu base image, and add Node.js later on.

[tobilg]

Another question is what you expect to be started with the Docker image start. I guess it's bin/spark-node? If so, the Docker container can be used interactively by supplying docker -i ... which would then start the Spark-Node REPL...

[henridf]

Starting bin/spark-node makes sense to me.

[tobilg]

Good. I think I can finish this tomorrow.

[tobilg]

I launched an automated build with the Docker Hub at https://hub.docker.com/r/tobilg/spark-node/

[henridf]

I'm assuming the "Full Description" section on the Docker Hub page doesn't automatically update with the readme from the repo? If that assumption is correct, I'd recommend changing it to a (briefer) description of the Docker image itself, with a pointer to the GitHub repo.
(Plus things like the "Requirements" section of the readme don't make sense on the Docker Hub page anyway).

[tobilg]

Actually, it does auto-update. I'd suggest that you open an account yourself, then you're flexible to change it like you want.

[henridf]

Are you saying I can modify the "Full Description" on https://hub.docker.com/r/tobilg/spark-node/? I have an account but I don't
see a way to do that.

On 27 November 2015 at 12:35, Tobi [email protected] wrote:

Actually, it does auto-update. I'd suggest that you open an account
yourself, then you're flexible to change it like you want.

—
Reply to this email directly or view it on GitHub
#14 (comment)
.

[tobilg]

You can only do that if you're the owner of the image. That's why I'm suggesting you should create your own image. I'll retract my image then.

[henridf]

Ah, thanks, that makes sense.

On 27 November 2015 at 13:24, Tobi [email protected] wrote:

You can only do that if you're the owner of the image. That's why I'm
suggesting you should create your own image. I'll retract my image then.

—
Reply to this email directly or view it on GitHub
#14 (comment)
.

[henridf]

Created image under my docker hub account as per @tobilg's suggestion and pointed README.md to it.

[henridf]

Closing this issue. Thanks @tobilg !

[tobilg]

What I noted is that I'm still stated as maintainer of the Docker image, and that the description on the Docker Hub is empty. Just to let you know...

[henridf]

Docker Hub description filled.

Re the maintainer in the Dockerfile, I left you as a way to acknowledge that you're the author.

But I could just as well put myself as maintainer and leave a comment right next to it naming you as the original author. What do you prefer?