-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose port 9997 #14
Comments
Known issues
|
thanks for working on this - for 'automate the build of the tarball', it would be good to check to see if it already exists in the user's .m2 - I believe people use this to run custom builds of geomesa so they may want a particular working branch to get deployed |
I suppose that this definition
and this dependency
.. they together guarantee that the tarball is only built if necessary, correct? |
Ah, I'm not sure - isn't BUILD_TARBALL a prerequisite for DIST_TARBALL then? I feel like there is another check required |
@elahrvivaz : No worries. I will test what happens when the artifact is already there, and when it is not. |
I'm a complete newbie on geomesa, so please pardon me for my language full of uncertainties and suppositions.
Background
I'm trying to run the accumulo tutorial which apparently needs port 9997.
In order to do that, apparently I have to expose port 9997 and rebuild the Docker image.
I had troubles building this image, mainly because bigtop repository version 1.1.0 apparently vanished.
About this ticket
This ticket is intended to tag the experiments I'm doing on the docker build process.
This is a list of modifications:
My changes are being done at:
https://github.com/frgomes/geodocker-geomesa/tree/0014-expose_port_9997
The text was updated successfully, but these errors were encountered: