Raynet One On-Premises Installation and Operations Guide

Important:

All commands in this section require the Raynet One stack to be running (containers must be started first).

Make sure you have already executed:

docker compose up -d

This section covers common operational tasks for managing Raynet One Docker containers.

Restart a Specific Service

To restart a single service (e.g. after changing configuration or to apply updates without affecting others), use the service name as defined in your docker-compose.yml file (under services:). This command only restarts the web UI container, all other containers keep running.

docker compose restart <service_name> (e.g., docker compose restart frontend)

Follow Logs

To follow the logs of a specific service in real-time (useful for debugging, monitoring startup issues, or observing behavior). This example shows real-time logs of the web UI container:

docker compose logs -f <service_name> (e.g., docker compose logs -f frontend)

Tip:

Press Ctrl+C to stop following the logs.

Recreate Containers (Force)

To force recreate all containers (e.g., after pulling new images, changing image tags, or when containers are in a inconsistent state):

docker compose up -d --force-recreate

When to use this command:

This forces Docker to recreate every container from scratch using the latest images and current compose configuration. It is useful when a simple restart does not solve the problem (e.g. containers that refuse to update). It applies any changes to the compose files (image tags, volumes, environment variables, etc.) without needing to run down + up.

Important:

Use this sparingly in production.

For normal updates prefer:

docker compose pull && docker compose up -d

This command ensures a completely fresh start with the current compose configuration.