Try it on your own computer

One command starts a private Ophiolite on this computer, with the well headers of three Dutch provinces (Groningen, Drenthe and Friesland: 2,222 wells from the public NLOG register) and one gamma-ray log to calculate with. Only this computer can reach it. It ends by printing a sign-in link; the link works once, signs you in and shows what to try next.

What you need

• A Linux computer with an x86_64 processor.
• Docker or Podman, with compose.
• Python 3.9 or later.
• About 6 GB of free disk and 4 GB of memory for the container engine.
• An internet connection the first time, to download the server and database images.

With Podman, start its service first:

systemctl --user start podman.socket

Start it

Open a terminal in an empty folder and run the line for your container engine.

The server image is not published yet, so there is no command to copy here. When it is, this page shows the command for Docker and for Podman.

The line downloads the server image, copies the operations tool out of it into this folder, checks that the tool, the sample and the setup files are the ones the image was released with, and starts the server and its database in a new folder named ophiolite-try. The first start takes a few minutes. Running the tool again from the same folder finishes an interrupted start and does not load anything twice.

Sign in again

Each link works once and only for 15 minutes. When it has been used or has expired, print a new one from the folder where you started:

python3 ophiolite-ops sign-in-link you --dir ophiolite-try

The start also printed this line with the full folder name.

Stop and remove it

python3 ophiolite-ops try down

This stops the server and removes its containers, its data and the folder it made. Files you put in that folder yourself are kept, and it names them. The operations tool stays in the folder where you started; delete it when you no longer need it. To remove the two downloaded images as well, run this line instead of the one above (after a plain down there is no evaluation left to name them, and it reports that there is nothing to remove):

python3 ophiolite-ops try down --images

The engine keeps an image that another container on this computer still uses, and the tool says so. To start again with fresh data on the same address:

python3 ophiolite-ops try reset

Troubleshooting

When the line stops before the tool is in the folder, the message comes from your container engine. Nothing is left behind: no tool, no container and no folder. Fix the cause and run the same line again.

• The engine is not installed. The terminal says the command is not found. Install Docker or Podman with compose.
  Technical details

  The message is docker: command not found or sh: 1: podman: not found.

• The engine is not running, or you may not use it. Start the engine, or use an account that may run containers.
  Technical details

  The message is Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?, permission denied while trying to connect to the docker API or Cannot connect to Podman. Start Docker with sudo systemctl start docker, or Podman with systemctl --user start podman.socket.

• The disk is full. Free about 6 GB and run the line again.
  Technical details

  The message ends with no space left on device.

• The image cannot be downloaded. Check the internet connection and that the line was copied whole.
  Technical details

  The message contains pull access denied, manifest unknown or unauthorized.

• The processor is not x86_64. The server image runs on x86_64 Linux only for now.
  Technical details

  The message contains exec format error or no matching manifest.

• The tool is already in this folder. The line never replaces it. It prints the line that starts from the tool that is there; run that one instead.
  Technical details

  The message starts with ophiolite-ops is already in this folder.

Once the tool is in the folder, it checks the computer before it starts anything. When it stops, it says what is wrong and the exact line to run next, and it removes whatever it made in that attempt; a start that stopped while loading the sample keeps what was loaded, and running the tool again finishes it.