Rework jade getting started #3675
Conversation
add some things to be noted
some more things to note
cernopendata/modules/fixtures/data/docs/jade-getting-started/jade-getting-started.md
Outdated
Show resolved
Hide resolved
cernopendata/modules/fixtures/data/docs/jade-getting-started/jade-getting-started.md
Outdated
Show resolved
Hide resolved
|
|
||
| ## <a name="vbox">"I have installed VirtualBox, downloaded JADE VM image and launched it. And now?"</a> | ||
| 1. Pull the image with `docker pull ghcr.io/andriish/fedora39x86_64i686_gnu:latest` |
There was a problem hiding this comment.
BTW do you plan to version the images later? The latest tag has a drawback in that it evolves over time, so does not persistently identify the version, see e.g. this essay. When the image get stable, and before the release, it might be good to use semantic versioning and introduce a tag such as 1.0 for persistence referencing to the image.
cernopendata/modules/fixtures/data/docs/jade-getting-started/jade-getting-started.md
Outdated
Show resolved
Hide resolved
| 2. Run the container `docker run -dit --platform linux/amd64 --name jade_soft -v $"(pwd)":/home ghcr.io/andriish/fedora39x86_64i686_gnu` \ | ||
| The `-v` option will mount the current directory (where it might be necessary to use `"$PWD"` instead of `$"(pwd)"` due to a special character error) to the home directory inside the container. It is thus useful to set the working directory to the cloned repository to conveniently run the software scripts and programs. \ | ||
| Note that not specifying a platform will result in the container software trying to run the image on the hosts platform type, while the image requires to be run on the linux/amd64 platform. The `-dit` (detached, interactive, tty) option is also necessary to keep the container running in the background and be interactive, else it might close immediately. | ||
| 4. Attach with `docker attach jade_soft` and run `sh jadeinstall.sh --bits=32` \ |
There was a problem hiding this comment.
Note that I'm getting the following error when I try to run the instructions:
[root@29a02bfa16e0 home]# sh ./jadeinstall.sh --bits=3
...
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
-- Found Threads: TRUE
-- Looking for Fortran sgemm
-- Looking for Fortran sgemm - not found
CMake Error at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
Could NOT find BLAS (missing: BLAS_LIBRARIES)
Call Stack (most recent call first):
/usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:600 (_FPHSA_FAILURE_MESSAGE)
/usr/share/cmake/Modules/FindBLAS.cmake:1383 (find_package_handle_standard_args)
CMakeLists.txt:36 (find_package)
-- Configuring incomplete, errors occurred!
Change Dir: '/home/build/jadesoft'
Run Build Command(s): /usr/bin/cmake -E env VERBOSE=1 /usr/bin/gmake -f Makefile -j2
gmake: Makefile: No such file or directory
gmake: *** No rule to make target 'Makefile'. Stop.
cmake build failedIs this expected? Does the container image lack some BLAS libraries that are needed for the script to run?
(Ideally, the image could come pre-built for various architectures, amd64 and arm64, so that peoplecould only pull the image and use it directly, without having to do the install part puerhaps?)
There was a problem hiding this comment.
It is unexpected, for me it works fine when I just follow the instructions.
Is the --bits=3 intentional? Maybe --bits=32 will fix it.
First real instructions on how to install the JADE software.