README.md

Full Development Docker Compose

Operating

Find our docs here.

Development

Rebuilding

To rebuild all services, run:

docker compose -f docker/dev-full/docker-compose.yml up -d --build

To rebuild just the server, run:

docker compose -f docker/dev-full/docker-compose.yml up -d --build rivet-server

Logs

To fetch logs for a service, run:

docker compose -f docker/dev-full/docker-compose.yml logs {name}

Following

To follow logs, run:

docker compose -f docker/dev-full/docker-compose.yml logs -f {name}

Grep

It's common to use grep (or the more modern ripgrep) to filter logs.

For example, to find all errors in rivet-server with the 10 preceding lines, run:

docker compose -f docker/dev-full/docker-compose.yml logs rivet-server | grep -B 10 level=error

Logs for rivet-server and rivet-client can also be configured via the environment. See here for more information.

Troubleshooting

Illegal instruction during apt-get install on macOS

If you see this output:

Updating certificates in /etc/ssl/certs...
Illegal instruction
Illegal instruction
dpkg: error processing package ca-certificates (--configure):
 installed ca-certificates package post-installation script subprocess returned error exit status 132
Setting up libgssapi-krb5-2:amd64 (1.20.1-2+deb12u2) ...
Setting up libcurl4:amd64 (7.88.1-10+deb12u8) ...
Setting up curl (7.88.1-10+deb12u8) ...
Processing triggers for libc-bin (2.36-9+deb12u9) ...
Errors were encountered while processing:
 ca-certificates
E: Sub-process /usr/bin/dpkg returned an error code (1)

Try changing your Docker VM to Docker VMM. See here for more information.

FoundationDB unhealthy on macOS

If you see this output:

Configuring database...
Starting FDB server on 172.19.0.10:4500
ERROR: Disk i/o operation failed (1510)
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
/var/fdb/scripts/fdb.bash: line 68:    38 Segmentation fault      fdbserver --listen-address 0.0.0.0:"$FDB_PORT" --public-address "$PUBLIC_IP:$FDB_PORT" --datadir /var/fdb/data --logdir /var/fdb/logs --locality-zoneid="$(hostname)" --locality-machineid="$(hostname)" --class "$FDB_PROCESS_CLASS"
Database already configured.
Starting FDB server on 172.19.0.10:4500
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
/var/fdb/scripts/fdb.bash: line 68:    32 Segmentation fault      fdbserver --listen-address 0.0.0.0:"$FDB_PORT" --public-address "$PUBLIC_IP:$FDB_PORT" --datadir /var/fdb/data --logdir /var/fdb/logs --locality-zoneid="$(hostname)" --locality-machineid="$(hostname)" --class "$FDB_PROCESS_CLASS"
Database already configured.
Starting FDB server on 172.19.0.10:4500
Error: Disk i/o operation failed
Database already configured.
Starting FDB server on 172.19.0.10:4500
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
/var/fdb/scripts/fdb.bash: line 68:    32 Segmentation fault      fdbserver --listen-address 0.0.0.0:"$FDB_PORT" --public-address "$PUBLIC_IP:$FDB_PORT" --datadir /var/fdb/data --logdir /var/fdb/logs --locality-zoneid="$(hostname)" --locality-machineid="$(hostname)" --class "$FDB_PROCESS_CLASS"
Database already configured.
Starting FDB server on 172.19.0.10:4500
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
/var/fdb/scripts/fdb.bash: line 68:    32 Segmentation fault      fdbserver --listen-address 0.0.0.0:"$FDB_PORT" --public-address "$PUBLIC_IP:$FDB_PORT" --datadir /var/fdb/data --logdir /var/fdb/logs --locality-zoneid="$(hostname)" --locality-machineid="$(hostname)" --class "$FDB_PROCESS_CLASS"
Database already configured.
Starting FDB server on 172.19.0.12:4500
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
/var/fdb/scripts/fdb.bash: line 68:    32 Segmentation fault      fdbserver --listen-address 0.0.0.0:"$FDB_PORT" --public-address "$PUBLIC_IP:$FDB_PORT" --datadir /var/fdb/data --logdir /var/fdb/logs --locality-zoneid="$(hostname)" --locality-machineid="$(hostname)" --class "$FDB_PROCESS_CLASS"

Try changing you Docker VM to Apple Virtualization framework with Use Rosetta and VirtioFS enabled.