Increase available shared memory in dev container

[martyngigg]

Description

Increases the available shared memory in development container when started with the mantid_development.sh script. The LoadEventNexusTest tests multi-process loading and requires more than the 64m of shared memory available that Docker makes available by default.

Testing

• Start a CentOS 7 development container and build DataHandlingTest
• Run the LoadEventNexusTest and it should pass. Before this it failed with a bus error.

[DavidFair]

I'm having some issues building locally with CentOS, are you seeing this as well on the latest image from docker hub?

CMake Error at buildconfig/CMake/PyQtFindImpl.cmake:61 (message):
  Error encountered while determining PyQt confguration:

  Traceback (most recent call last):

    File "/mantid_build/mantid/buildconfig/CMake/FindPyQt.py", line 108, in <module>
      sys.exit(main())
    File "/mantid_build/mantid/buildconfig/CMake/FindPyQt.py", line 98, in main
      print(PyQtConfig('PyQt%d' % args.version))
    File "/mantid_build/mantid/buildconfig/CMake/FindPyQt.py", line 27, in __init__
      qtcore = __import__(name + '.QtCore', globals(), locals(), ['QtCore'], 0)

  ModuleNotFoundError: No module named 'PyQt5'

Call Stack (most recent call first):
  buildconfig/CMake/FindPyQt5.cmake:24 (find_pyqt)
  CMakeLists.txt:153 (find_package)

[martyngigg]

@DavidFair It seems okay for me. Can we check we have the same image locally?

$ docker inspect mantidproject/mantid-development-centos7:latest | grep -i -A 2 digest
        "RepoDigests": [
            "mantidproject/mantid-development-centos7@sha256:2a25e9aa1802736250b85a1248540e11f38693ed1c39aa13233b173d7c7ddce5"
        ],

[DavidFair]

I seem to have had a different image tagged as latest, a complete clean-up and pull fixed it.

This works for me :+1: