-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
Failed to expose service when an ambassador container already exists #200
Comments
Try doing I'll keep this ticket open since we should error better when the container exists but is stopped for whatever reason. |
@josegonzalez
I used dokku ansible to install dokku, and had to run the playbook multiple times because of some errors. Maybe that is the reason why that dead container exists. |
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes #200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes #200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes #200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
… don't have expose configuration Closes dokku/dokku-redis#200
I have issues exposing the elasticsearch container on a remote server.
Here are the commands:
The expose command produces this error:
Still I try to run this command on my local machine to access the server using an ssh tunnel:
But the site
http://127.0.0.1:9200/
still cannot be reached. I use similar methods to expose postgres and redis and they all work. No luck with elasticsearch.This is the result of
docker container ls
. It looks like elasticsearch ambassador fails to be created.dokku elasticsearch:info es:
The text was updated successfully, but these errors were encountered: