3
0
mirror of https://github.com/ergochat/ergo.git synced 2024-12-22 18:52:41 +01:00
ergo/distrib/docker
Chris Smith 69e1dea224
Fix ports in the docker instructions
-P/--publish-all publishes the container ports on a random
host port, which you have to look up using `docker port`.

In the common case they should be published on the same ports.
2019-11-22 18:06:51 +00:00
..
docker-compose.yml Merge in files from docker repository. 2019-11-22 17:48:53 +00:00
Dockerfile Merge in files from docker repository. 2019-11-22 17:48:53 +00:00
README.md Fix ports in the docker instructions 2019-11-22 18:06:51 +00:00
run.sh Merge in files from docker repository. 2019-11-22 17:48:53 +00:00

Oragono Docker

This folder holds Oragonos Dockerfile and related materials. Oragono is published iautomatically to Docker Hub at oragono/oragano.

The latest tag tracks the stable branch of Oragono, which contains the latest stable release. The dev tag tracks the master branch, which may by unstable and is not recommended for production.

You can see other tags on Docker Hub if you wish to run a specific version of Oragono.

Quick start

The Oragono docker image is designed to work out of the box - it comes with a usable default config and will automatically generate self-signed TLS certificates. To get a working ircd, all you need to do is run the image and expose the ports:

docker run --name oragono -d -p 6667:6667 -p 6697:6697 oragono/oragono:tag

This will start Oragono and listen on ports 6667 (plain text) and 6697 (TLS). The first time Oragono runs it will create a config file with a randomised oper password. This is output to stdout, and you can view it with the docker logs command:

# Assuming your container is named `oragono`; use `docker container ls` to
# find the name if you're not sure.
docker logs oragono

You should see a line similar to:

Oper username:password is dan:cnn2tm9TP3GeI4vLaEMS

Persisting data

Oragono has a persistent data store, used to keep account details, channel registrations, and so on. To persist this data across restarts, you can mount a volume at /ircd.

For example, to create a new docker volume and then mount it:

docker volume create oragono-data
docker run -d -v oragono-data:/ircd -p 6667:6667 -p 6697:6697 oragono/oragono:tag

Or to mount a folder from your host machine:

mkdir oragono-data
docker run -d -v $(PWD)/oragono-data:/ircd -p 6667:6667 -p 6697:6697 oragono/oragono:tag

Customising the config

Oragonos config file is stored at /ircd/ircd.yaml. If the file does not exist, the default config will be written out. You can copy the config from the container, edit it, and then copy it back:

# Assuming that your container is named `oragono`, as above.
docker cp oragono:/ircd/ircd.yaml .
vim ircd.yaml # edit the config to your liking
docker cp ircd.yaml oragono:/ircd/ircd.yaml

You can use the /rehash command to make Oragono reload its config, or send it the HUP signal:

docker kill -HUP oragono

Using custom TLS certificates

TLS certs will by default be read from /ircd/tls.crt, with a private key in /ircd/tls.key. You can customise this path in the ircd.yaml file if you wish to mount the certificates from another volume. For information on using Lets Encrypt certificates, see this manual entry.

Using docker-compose

This folder contains a sample docker-compose file which can be used to start an Oragono instance with ports exposed and data persisted in a docker volume. Simply download the file and then bring it up:

curl -O https://raw.githubusercontent.com/oragono/oragono/master/distrib/docker/docker-compose.yml
docker-compose up -d

Building

If you wish to manually build the docker image, you need to do so from the root of the Oragono repository (not the distrib/docker directory):

docker build -f distrib/docker/Dockerfile .