https://github.com/dokku/docker-ambassador

A maintained version of the ambassador linking pattern
https://github.com/dokku/docker-ambassador

ambassador docker docker-image dokku paas

Last synced: 2 days ago
JSON representation

A maintained version of the ambassador linking pattern

• Host: GitHub
• URL: https://github.com/dokku/docker-ambassador
• Owner: dokku
• License: mit
• Created: 2019-03-05T16:22:29.000Z (over 5 years ago)
• Default Branch: main
• Last Pushed: 2024-09-22T03:48:20.000Z (about 2 months ago)
• Last Synced: 2024-10-30T00:56:02.044Z (8 days ago)
• Topics: ambassador, docker, docker-image, dokku, paas
• Language: Shell
• Homepage:
• Size: 134 KB
• Stars: 8
• Watchers: 4
• Forks: 6
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# docker-ambassador

[![dokku/ambassador](http://dockeri.co/image/dokku/ambassador)](https://hub.docker.com/r/dokku/ambassador)

A maintained version of the [ambassador linking](https://github.com/SvenDowideit/dockerfiles/tree/master/ambassador) pattern.

This ambassador image can be used to automatically proxy all exposed ports from the linked container, or to proxy a specified port at a specific IP address or hostname.

## Use Docker linking to autoattach to all exposed ports

```shell

# start a container that exposes a port

docker run --rm --name nginx.1 nginx

# run the ambassador 

docker run --rm -ti --link nginx.1 -p 9999:80 -p 8888:443 dokku/ambassador

```

Running the ambassador container will result in output lke the following.

```text

Connecting to 172.17.0.4:80 172.17.0.4:443...

2016/01/12 13:03:14 socat[19] E connect(5, AF=2 172.17.0.4:443, 16): Connection refused

```

You can also proxy exposed ports from more than one container by using more than one --link, but only if there is no duplication of exposed container ports.

## Specify host and port

This will allow you Dynamically map a container port after its been created.

For example:

```shell

# start a container that exposes a port

docker run --rm --name nginx.1 nginx

```

In the above example, nginx is running, but no-one can make requests to it. By running:

```shell

# Assuming the nginx.1 container is on IP `172.17.0.4`

docker run --rm -p 9999:80 dokku/ambassador 172.17.0.4 80

```

You will now be able to make requests to the web server on `http://localhost:9999`

## Credit

Thanks to Sven Dowideit for providing the initial implementation.