3 min • read

Run the demo with Docker

In this Docker quickstart guide, we'll get Emissary-ingress running locally with a demo configuration. In the next section, we'll then walk through how to deploy Emissary-ingress in Kubernetes with a custom configuration.

1. Running the demo configuration

By default, Emissary-ingress uses a demo configuration to show some of its basic features. Get it running with Docker, and expose Emissary-ingress on port 8080:

2. Emissary-ingress's diagnostics

Emissary-ingress provides live diagnostics viewable with a web browser. While this would normally not be exposed to the public network, the Docker demo publishes the diagnostics service at the following URL:


You'll have to authenticate to view this page: use the username admin, password admin (obviously this would be a poor choice in the real world!). We'll talk more about authentication shortly.

To access the Diagnostics page with authentication, use curl http://localhost:8080/ambassador/v0/diag/ -u admin:admin

Some of the most important information - your Emissary-ingress version, how recently Emissary-ingress's configuration was updated, and how recently Envoy last reported status to Emissary-ingress - is right at the top. The diagnostics overview can show you what it sees in your configuration map, and which Envoy objects were created based on your configuration.

3. The Quote service

Since Emissary-ingress is a comprehensive, self-service edge stack, its primary purpose is to provide access and control to microservices for the teams that manage them. The demo is preconfigured with a mapping that connects the /qotm/ resource to the "Quote" service -- a demo service that supplies quotations. You can try it out by opening


in your browser, or from the command line as

This request will route to the qotm service at demo.getambassador.io, and return a random quote.

You can see details of the mapping by clicking the blue http://localhost:8080/qotm/ link at the very bottom of the Ambassador Route Table in the diagnostics overview.

4. Authentication

On the diagnostic overview, you can also see that Emissary-ingress is configured to do authentication -- in the middle of the overview page, you'll see the Ambassador Services In Use section, and you can click the tcp:// link for details on the AuthService configuration. This demo auth service is running inside the Docker container with Emissary-ingress and the Quote service, and Emissary-ingress uses it to mediate access to everything behind Emissary-ingress.

You saw above that access to the diagnostic overview required you to authenticate as an administrator. Getting a random quote does not require authentication, but to get a specific quote, you'll have to authenticate as a demo user. To see this in action, open


in your browser. From the command line, you can see that:

will return a 401, but

will succeed. (Note that that's literally "username" and "password" -- the demo auth service is deliberately not very secure!)

Note that it's up to the auth service to decide what needs authentication -- teaming Emissary-ingress with an authentication service can be as flexible or strict as you need it to be.

Next steps

We've just walked through some of the core features of Emissary-ingress in a local configuration. To see Emissary-ingress in action on Kubernetes, check out the Installation Guide.