Removed container-maker references.

scripts/ci/jobs/ci_images.yml

 .ci_images_changes: &ci_images_changes
   changes:
-    - ThirdParty/container-maker
     - scripts/ci/jobs/ci_images.yml
     - scripts/docker/saxon/**/*
     - scripts/docker/Dockerfile.pre-commit
     - scripts/docker/Dockerfile.web
-    - web/data/versions.json
 
 ci_images:
   stage: preparation

web/.linksrc.json

@@ -2,7 +2,6 @@
   "excludePatterns": [
     "^https?://.*localhost",
     "^https?://github.com/ufz/ogs/releases/.*",
-    "https://jenkins.opengeosys.org/job/ufz/job/ogs-container-maker/job/master/build",
     "https://dev.azure.com/ogsci/ogs/_build",
     "https://ogs.jfrog.io/ogs"
   ]

web/content/docs/devguide/environments/docker/index.md

-+++
-date = "2018-02-26T11:00:13+01:00"
-title = "Docker"
-author = "Lars Bilke"
-weight = 1050
-
-aliases = ["/docs/devguide/advanced/docker"]
-
-[menu]
-  [menu.devguide]
-    parent = "environments"
-+++
-
-## Introduction
-
-<!-- vale off -->
-> Docker containers wrap up a piece of software in a complete filesystem that contains everything it needs to run: code, runtime, system tools, system libraries – anything you can install on a server. This guarantees that it will always run the same, regardless of the environment it is running in.
->
-> <cite>[www.docker.com/whatisdocker](https://www.docker.com/whatisdocker)</cite>
-<!-- vale on -->
-
-See the [docs](https://docs.docker.com/get-docker/) for installation instructions (if you are on Windows we highly recommend the [Docker Desktop WSL 2 backend](https://docs.docker.com/docker-for-windows/wsl/)).
-
-## Images
-
-Docker images can be created by [Dockerfiles](https://docs.docker.com/engine/reference/builder/) which can be stacked and thus form a directed graph. OGS-6 image definitions are created with [`ufz/ogs-container-maker`](https://github.com/ufz/ogs-container-maker). Built images can be found at the [GitLab Container Registry](https://gitlab.opengeosys.org/ogs/ogs/container_registry). You can also [create images from your local source code](https://github.com/ufz/ogs-container-maker#build-ogs-from-local-git-repo).
-
-To build an image by yourself create a Dockerfile:
-
-```bash
-FROM ubuntu:20.04
-
-RUN ...
-```
-
-Run the `build` command:
-
-```bash
-docker build -t repo/image_name path/to/directory
-```
-
-- `-t` specifies a name for the image, can be arbitrary chosen (but should match the corresponding image on Docker Hub if there is one)
-- The path should specify the directory where the Dockerfile is located
-
-Now you can see your build image with `$ docker images`.
-
-## Run a container
-
-To run commands inside a container:
-
-```bash
-docker run --rm image_name command_to_run
-```
-
-- `--rm` Cleans up after exiting the container
-
-To run an interactive shell add the `-it`-switch:
-
-```bash
-docker run --rm -it image_name
-```
-
-It is useful to mount folders from the host operating system in the Docker container, e.g. to edit source code on your host with your favorite editor:
-
-```bash
-docker run --rm -it -v /host/directory:/container/directory image_name
-```
-
-## Prebuilt OGS-6 Docker images
-
-There are docker images provided on the [GitLab Container Registry](https://gitlab.opengeosys.org/ogs/ogs/container_registry) which include everything necessary to build OGS-6 (e.g. `registry.opengeosys.org/ogs/ogs/gcc`). They are used by the CI but you can also use them for development. For running the images require CPU capabilities equivalent or better than the Intel Ivybridge[^1] architecture.
-
-Even better for development is the usage of [Singularity container]({{< relref "singularity.md" >}}) because they offer a transparent mapping of the user to container space.
-
-[^1]: From [GCC docs](https://gcc.gnu.org/onlinedocs/gcc/gcc-command-options/machine-dependent-options/x86-options.html): *Intel Ivy Bridge CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, CX16, SAHF, FXSR, AVX, XSAVE, PCLMUL, FSGSBASE, RDRND and F16C instruction set support.*

web/content/docs/devguide/packages/python-env/index.md

@@ -13,7 +13,6 @@ aliases = ["/docs/devguide/advanced/python-env"]
 
 In OGS we make use of Python packages at different stages, e.g.:
 
-- [ogs-container-maker](https://gitlab.opengeosys.org/ogs/container-maker) when the CI prepares its environment
 - [TESPy]({{< ref "3d_3bhes_array.md#tespy" >}}) for simulating thermal engineering plants in a benchmark
 - [pvpython](https://kitware.github.io/paraview-docs/latest/python/) for pre- and post-processing
 - [nbconvert](https://nbconvert.readthedocs.io/en/latest/) for testing Jupyter Notebooks

web/content/docs/devguide/testing/gitlab-ci/index.md

@@ -24,8 +24,6 @@ Each pipeline run is visualized as follows:
 
 Jobs belong to a stage and each job will get a status (success, warnings, failure). Some jobs are optional (see the gear icon) and can be manually triggered by pressing the play button.
 
-Some jobs run on native servers (e.g. on the `envinf[1,2,3]` Linux servers) and some run in [Docker containers]({{< relref "docker.md#prebuilt-ogs-6-docker-images" >}}).
-
 ## Automatic testing
 
 The master-branch of the main repository as well as all merge requests on that repository are automatically tested. See [the pipelines page](https://gitlab.opengeosys.org/ogs/ogs/pipelines).

web/content/docs/userguide/basics/container/index.md

@@ -37,7 +37,14 @@ Simply download an image from the [releases]({{< ref "/releases" >}}) page.
 
 #### Option: Download image from the latest master-branch build
 
-Simply download an image from the [latest master-branch build](https://gitlab.opengeosys.org/ogs/ogs/-/jobs/artifacts/master/browse/ThirdParty/container-maker/_out/images?job=container) page.
+Simply download an image from the latest master-branch build:
+
+<!-- vale off -->
+* [ogs-serial.squashfs](https://minio.ufz.de/ogs/public/container/ogs/master/ogs-serial.squashfs)
+* [ogs-petsc.squashfs](https://minio.ufz.de/ogs/public/container/ogs/master/ogs-petsc.squashfs) (with PETSC-support)
+<!-- vale on -->
+
+Please note that these images have `.squashfs` as the file ending. Usage is the same as with `.sif`-files.
 
 ### Run OGS inside a Container (called from outside)