.. | ||
img | ||
binary.md | ||
from-source.md | ||
helm.md | ||
kubernetes.md | ||
readme.md | ||
synology.md |
title | lang | meta | |||||
---|---|---|---|---|---|---|---|
Docker | en-US |
|
Pomerium using Docker
In the following quick-start, we'll create a minimal but complete environment for running Pomerium with containers.
Prerequisites
- A configured identity provider
- Docker and docker-compose
- TLS certificates
Configure
Configuration file
Create a configuration file (e.g config.yaml
) for defining Pomerium's configuration settings, routes, and access-policies. Consider the following example:
<<< @/examples/config/config.minimal.yaml
Ensure the docker-compose.yml
contains the correct path to your config.yaml
.
Autocert Docker-compose
Ensure you have set up the requisite DNS and port forwarding in TLS certificates
Download the following docker-compose.yml
file and modify it to:
- generate new secrets
- mount your TLS certificates
- mount your
config.yaml
configuration file - Set
autocert_use_staging
tofalse
once you have finished testing
<<< @/examples/docker/autocert.docker-compose.yml
Please note that you should use a persistent volume to store certificate data, or you may exhaust your domain quota on Let's Encrypt.
Wildcard Docker-compose
Download the following docker-compose.yml
file and modify it to:
- generate new secrets
- mount your TLS certificates
- mount your
config.yaml
configuration file
<<< @/examples/docker/basic.docker-compose.yml
Run
Finally, simply run docker compose.
docker-compose up
Docker will automatically download the required container images for Pomerium and httpbin. Then, Pomerium will run with the configuration details set in the previous steps.
You should now be able access to the routes (e.g. https://httpbin.corp.yourdomain.example
) as specified in your policy file.
You can also navigate to the special pomerium endpoint httpbin.corp.yourdomain.example/.pomerium/
to see your current user details.