blob: 9334909f42dca0367896b9f38855ce6c28b54c31 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
|
Given a docker image 'catlfish' as defined in
catlfish/packaging/docker, here is an example of a minimal catlfish
log using one docker container to run one single Erlang beam instance
for both a frontend and a storage node and an example of how to start
a shell script in the host system performing merge periodically.
Create the docker image
$ docker build -t my-single-image-catlfish docker
Run the newly created image in a docker container
$ docker run --name=my-catlfish --detach=true --publish 127.0.0.1:8080-8082:8080-8082/tcp my-single-image-catlfish
This will create and start one container listening for cert chain
submissions on https://127.0.0.1:8080/.
In order to start a shell script doing merge (i.e. generate new STH's)
with an interval of 20 minutes (with the first merge occuring five
minutes after startup) in the host system, cd into the catlfish
directory and run examples/docker-minimal/docker/merge.sh.
To submit a cert chain and verify the resulting SCT, try the
submitcert tool:
$ tools/submitcert.py --store=tools/testcerts/cert1.txt --check-sct --sct-file=/tmp/cert1-sct https://127.0.0.1:8080/
Where are the log files? Try running a shell in the container and poke
around in the /opt/catlfish/log directory. Here's how to start one:
$ docker exec -it my-catlfish /bin/bash
|
