- Path where digital twins are mounted (default: `/project-blue/workspaces`)
## How to run this container
Once Docker is running use this command
`docker run registry1.dso.mil/ironbank/beast-code/project-blue/base-image`
Currently the only platform data that is compatible with this container by default is the uss-never-sleeps and it must be mounted at
`/project-blue/workspaces/uss-never-sleeps` inside the container at runtime.
In order to use other platform data (also known as workspaces) with Project Blue
the `Workspace.DefaultWorkspace` field in `/project-blue/appsettings.Production.json` must be changed to match the folder name containing the platform data.
## Troubleshooting tips
If you are having trouble starting the container you can debug into it by altering the entrypoint like this.
`docker run -it --rm --name debug-project-blue --entrypoint=sh registry1.dso.mil/ironbank/beast-code/project-blue/base-image`
The server can be launched from the account `benjo` in the default working directory `/project-blue` using the executable `/project-blue/ProjectBlueServer`
If the executeable fails to launch, try running `ldd /project-blue/ProjectBlueServer` and verify that all of the necessary runtime dynamically linked libraries (DLLs) are present in the image.
We use `/usr/local/bin/dumb-init` as the default entrypoint in order to forward normal signals to and from the ProjectBlueServer executeable such as SIGTERM and SIGINT.
See https://github.com/Yelp/dumb-init for more information.
