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

To open or to not open public ports #23

Closed
pascalandy opened this issue Oct 1, 2017 · 15 comments
Closed

To open or to not open public ports #23

pascalandy opened this issue Oct 1, 2017 · 15 comments

Comments

@pascalandy
Copy link
Contributor

It make sense to open grafana port to the public.

But I'm not not sure to understand why prometheus and alertmanager have their port public. Any particular reason for this behaviour?

Many cheers!

@pascalandy pascalandy changed the title Open or not to open public ports To open or to not open public ports Oct 1, 2017
@stefanprodan
Copy link
Owner

I'm guessing you want to view alerts and be able to silence them, as for Prometheus you can monitor the targets, write queries and more. I will update the project and I'll include a reverse proxy with basic auth for those two.

@stefanprodan
Copy link
Owner

@pascalandy I've added the reverse proxy with basic auth, can you please test it out?

@pascalandy
Copy link
Contributor Author

On it.

@pascalandy
Copy link
Contributor Author

Cannot start compose.

root@vps01:~/dockprom# docker-compose up -d
ERROR: Invalid interpolation format for "environment" option in service "caddy": "ADMIN_USER=${ADMIN_USER:-admin}"

@stefanprodan
Copy link
Owner

Looks like inline defaults are supported in compose 2.1, should work now.

@pascalandy
Copy link
Contributor Author

humm

ERROR: Version in "./docker-compose.yml" is unsupported. You might be seeing this error because you're using the wrong Compose file version. Either specify a version of "2" (or "2.0") and place your service definitions under the services key, or omit the version key and place your service definitions at the root of the file to use version 1.
For more on the Compose file format versions, see https://docs.docker.com/compose/compose-file/
Aborting due to errexit on line 26. Exit code: 1

@stefanprodan
Copy link
Owner

can you please post docker-compose -v

@pascalandy
Copy link
Contributor Author

pascalandy commented Oct 1, 2017

On 1.8.0 and I see we are now at 1.16.1 !
https://github.com/docker/compose/releases

Compose is not updated along new docker installs? I wasn't aware.

@stefanprodan
Copy link
Owner

No, compose comes only with Docker for Mac, on linux you have to update via:

curl -L https://github.com/docker/compose/releases/download/1.16.1/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose
chmod +x /usr/local/bin/docker-compose

@pascalandy
Copy link
Contributor Author

pascalandy commented Oct 1, 2017

Updated. Compose is running.
EDIT - wip

@stefanprodan
Copy link
Owner

stefanprodan commented Oct 1, 2017

That's because you are running the older version with alermanager exposing port 9093.

You have to remove the stack with:

docker-compose down -v

And run the new one with:

ADMIN_USER=admin ADMIN_PASSWORD=admin docker-compose up -d

After that your prometheus and alermanager services will require user/pass.

@stefanprodan
Copy link
Owner

Ok, thanks for testing, I've updated the readme with the minimum required Docker Compose version.

@pascalandy
Copy link
Contributor Author

pascalandy commented Oct 2, 2017

Sorry for the confusion earlier. I meant, compose is now installed properly.

All the container behave normally. But there is nothing on those 3 ports :-/

  • Prometheus (metrics database) http://:9090
  • AlertManager (alerts management) http://:9093
  • Grafana (visualize metrics) http://:3000

I also run other stuff with traefik and webapps are responding normally.

Also, I'm very happy to help and to test this stack. It's a great one and it will actually help me to get shit/infra together :-p

@stefanprodan
Copy link
Owner

It was problem with the mount point for Caddy, should work now.

@pascalandy
Copy link
Contributor Author

pascalandy commented Oct 2, 2017

Yes! This is now solid :)

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

2 participants