Skip to content

Commit

Permalink
Merge branch 'master' of github.com:chrisruffalo/gudgeon
Browse files Browse the repository at this point in the history
  • Loading branch information
chrisruffalo committed Jun 7, 2019
2 parents f4d3ffe + b2d04f9 commit 1b791de
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ Gudgeon has a [COPR repository](https://copr.fedorainfracloud.org/coprs/cruffalo
### Docker Releases
Gudgeon also comes in container form from `gudgeon/gudgeon`.

The Docker container exposes ports 5354 (dns) and 9009 (http) and those ports should be published via the `docker` command. Remember to use `/tcp` and `/udp` when exposing the DNS ports. For persisting/modifying the configuration and for persisting data, metrics, and logs there are two directories in the container. The first directory `/etc/gudgeon` is for configuration files. The data is stored in `/var/lib/gudgeon`. The version can be any tag v0.3.13 or later. See the [docker hub](https://cloud.docker.com/u/gudgeon/repository/docker/gudgeon/gudgeon) page for tags and more details.
The Docker container exposes ports 5354 (dns) and 9009 (http) and those ports should be published via the `docker` command. Remember to use `/tcp` and `/udp` when exposing the DNS ports. For persisting/modifying the configuration and for persisting data, metrics, and logs there are two directories in the container. The first directory `/etc/gudgeon` is for configuration files. The data is stored in `/var/lib/gudgeon`. The version can be any tag v0.3.13 or later. See the [docker hub](https://hub.docker.com/r/gudgeon/gudgeon) page for tags and more details.

```bash
[user@host] docker run -ti -p 53:5354/tcp -p 53:5354/udp -p 9009:9009 -v /etc/gudgeon:/etc/gudgeon -v /var/lib/gudgeon:/var/lib/gudgeon gudgeon/gudgeon:${version}
Expand Down Expand Up @@ -88,4 +88,4 @@ With the prerequisites installed you can build Gudgeon by...
The `download` target is used to download new dependencies when needed. The `prepare` target is only needed if the required Go tools change. The output of the process is a statically compiled for a few different platforms. The binary is statically compiled to make it easily portable to platforms and other systems that do not have libc, recent Golang compilers, or other required libraries.

## License
[![FOSSA Status](https://app.fossa.io/api/projects/git%2Bgithub.com%2Fchrisruffalo%2Fgudgeon.svg?type=large)](https://app.fossa.io/projects/git%2Bgithub.com%2Fchrisruffalo%2Fgudgeon?ref=badge_large)
[![FOSSA Status](https://app.fossa.io/api/projects/git%2Bgithub.com%2Fchrisruffalo%2Fgudgeon.svg?type=large)](https://app.fossa.io/projects/git%2Bgithub.com%2Fchrisruffalo%2Fgudgeon?ref=badge_large)

0 comments on commit 1b791de

Please sign in to comment.