This repository provides some recipes to build containers for code_aster:

• for docker.

• for singularity.

It should be considered as a work in progress.

For example, additional work is needed to execute a containerized version of code_aster from an existing salome_meca installation.

The repository contains recipes to build a sequential and a parallel version for the development branch (default) which refers to the latest tag on docker images. The code_aster version is named unstable.

Executable images:

• codeastersolver/codeaster-seq: Sequential version of code_aster.

• codeastersolver/codeaster-mpi: Parallel version of code_aster.

Intermediate layer with prerequisites:

• codeastersolver/codeaster-common: Prerequisites for the sequential and parallel versions.

This image can also be used to build your own development version.

Singularity recipes are simple conversions that use the Docker images as bootstrap.

• latest: It refers to the last head of the default branch.

No more for the moment...

See available targets:

make

Then choose your target between seq and mpi, or build to build all:

make build

Environment files added in the env.d directory are sourced before calling docker/singularity builder. It may be useful for example to configure the environment to pass a proxy.

docker run --rm -it codeastersolver/codeaster-seq:latest

docker run --rm codeastersolver/codeaster-seq:latest as_run --nodebug_stderr --test zzzz100f

In this example the data files are extracted from the image. In the real life, these files are for example created from salome_meca.

# create a temporary container to access the testcase files
docker run --name astercp codeastersolver/codeaster-seq:latest

# copy files
mkdir workdir
docker cp astercp:/scif/apps/aster/share/aster/tests/sslv155a.comm workdir/
docker cp astercp:/scif/apps/aster/share/aster/tests/sslv155a.mmed workdir/

# clean the temporary container
docker rm astercp

# create the export file
docker run --rm  codeastersolver/codeaster-seq:latest as_run --get_export sslv155a --nodebug_stderr | \
    sed -e 's#/scif/apps/aster/share/aster/tests#.#g' \
    > workdir/export

If the export file is manually created, the version can be addressed just by name (P version unstable).

Now, run a code_aster container using local files:

docker run --rm --volume $(pwd)/workdir:/aster codeastersolver/codeaster-seq:latest \
    as_run --nodebug_stderr /aster/export

To limit the size of the binary images only few testcases are available in the installation directory. The 3800+ testcases can be extracted from the source tree from the Bitbucket repository (see below). Checking all the 3800 testcases takes about 15-20h cpu.

Some prerequisites are not yet available within the container (miss3d, ecrevisse, etc.). So, all the tests that are using these tools are currently in failure.

To execute the existing testcases, use:

docker run -t codeastersolver/codeaster-seq:latest run_testcases unstable

# to copy the result files
docker cp -a <CONTAINER>:/home/aster/resutest <DESTINATION>

Use the following commands to download all the 3800+ testcases from the Bitbucket repository and execute them.

# download the testcases out of the container
wget https://bitbucket.org/code_aster/codeaster-src/get/default.tar.gz
tar xzf default.tar.gz
mv code_aster-codeaster-src-*/astest . && rm -rf code_aster-codeaster-src-*

# mount 'astest' and run testcases in the container
docker run -t --volume $(pwd)/astest:/home/aster/tests codeastersolver/codeaster-seq:latest \
    run_testcases --tests=/home/aster/tests unstable