Julian Giordani

Hi @hezhiqiang8909, CMAKE can't find the PETSC installation successfully, can you try another version of Petsc. Currently for UW-2.13 we recommend using `petsc/3.17.1`, I notice you have `PETSc/3.17.4`

cmake looks for a .pc file at `$PETSC_DIR/lib/pkgconfig/PETSc.pc` Is this file on your machine at that location?

Can you send through this `/home/cloudam/underworld2-2.13.0b/build/temp.linux-x86_64-cpython-310_libUnderworld/CMakeFiles/CMakeOutput.log`

Thanks for the log file, unfortunately it didn't help pin point the problem. I think something unexpected is occurring with cmake(pkg-config), easybuild and petsc. To debug more, could you modify...

@hezhiqiang8909 can you try this file: https://github.com/underworldcode/underworld2/blob/6d8821c5287ae6cc84d541fe50265539eb2de875/underworld/libUnderworld/CMakeLists.txt Copy it into path `underworld2-2.13.0b/underworld/libUnderworld/CMakeLists.txt` I tweaked how CMAKE uses the PKG_CONFIG_PATH. Then run `pip install . -vvv` (instead of `python setup.py build`)...

@hezhiqiang8909, did the above change to `CMakeLists.txt` help? Let me know if you need help with it?

Hi Simon, Much appreciated for the detailed feedback on this. Yeah it's suboptimal! I'm happy to look at the docker MPI environment from the Underworld end and investigate possible improvements....

Hi Patrice, I remember we talked about this issue a month back and we turned off the passive tracers as they were causing issues after restart. Is this new case...

Don't merge yet, until we a satisfied the new dockers on dockerhub are correct.

Specifying multiple platforms in the docker-build-push action seems to do the job of the docker manifest commands that were previously there. I tested by building & pushing a test dockers...