Container Management

Starting

First Run vs. Subsequent Starts

On first run use the helper script, which also creates the required directories:

bash start.sh

For subsequent starts the compose command is enough:

docker compose --profile default up -d

Inspecting

docker compose ps
docker compose logs -f core-service

Stopping and cleaning up

docker compose --profile default down

Volume Deletion

Add -v to also drop volumes — safe in development, destructive in production. Use only when you’re certain all data has been backed up.

Common gotchas

Configuration Issues

Common problems and fixes:

• Ports in use — the stack binds 8080 (UI) and the core-service port. Stop conflicting services or remap in .env.
• Permissions on GPFS — if the container can’t read imported data, check that the host’s MAGELLON_GPFS_PATH is owned/readable by the compose user.
• GPU access — requires the NVIDIA container toolkit on the host.