Skip to content
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

password #1

Open
geoHeil opened this issue Jan 27, 2017 · 6 comments
Open

password #1

geoHeil opened this issue Jan 27, 2017 · 6 comments

Comments

@geoHeil
Copy link

geoHeil commented Jan 27, 2017

Hi, what is the password for the geodocker accumulo container?
I created a fork to upgrade to 1.8 and play with geomesa https://github.com/geoHeil/geodocker-geomesa but have problems logging in via user root and password GisPwd

What are the correct credentials?

@pomadchin
Copy link
Member

@geoHeil
Copy link
Author

geoHeil commented Jan 27, 2017

Indeed, I know that
ACCUMULO_PASSWORD: GisPwd
is set to that value. That's why I am using it here https://github.com/geoHeil/geodocker-geomesa

to launch it like

java -cp geomesa-quickstart-accumulo/target/geomesa-quickstart-accumulo-1.3.0.jar \
  com.example.geomesa.accumulo.AccumuloQuickStart \
  -instanceId accumulo \
  -zookeepers zookeeper \
  -user root \
  -password GisPwd \
  -tableName quickstart

which still fails (after adding the jars for geomesa)
ERROR: for accumulo-master Cannot start service accumulo-master: oci runtime error: container_linux.go:247: starting container process caused "exec: \"/sbin/geomesa-entrypoint.sh\": permission denied"

Additionally, I could ovserve that accumulo monitor was not able to obtain the traces due to the same issue.

@pomadchin
Copy link
Member

@geoHeil i think you have not valid permission for the entrypoint.sh, double check that it's executable.

@jnh5y
Copy link
Collaborator

jnh5y commented Jan 27, 2017

@geoHeil, @anthonyccri might be able to help.

Which docker images are you running? @anthonyccri published the GeoMesa GeoDocker and has used them successfully from AWS's EMR. I haven't had a chance to try them out locally...

@pomadchin
Copy link
Member

pomadchin commented Jan 27, 2017

I feel like it can be a problem of building image locally (wrong permissions).
Another problem can be that image is built on mac and mac docker can be buggy sometimes.

Figured out: potentially it's a typo in a docker file.

@geoHeil
Copy link
Author

geoHeil commented Jan 28, 2017

Indeed, I can confirm it is a typo in the entrypoint of the docker file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants