platform question

[droeatpm]

Since ignis-submit calls exec ${IGNIS_HOME}/backend/jre/bin/java and that java is for x86-64 linux, does that mean that is the only OS that can be used?

[cesarpomar]

The reason ignis-submit calls exec ${IGNIS_HOME}/backend/jre/bin/java, which is intended for x86-64 Linux, is that the precompiled Docker images available on DockerHub are designed for x86-64 architecture. Consequently, the Java version inside the container is tailored for this architecture. If you wish to use other architectures, you will need to build the environment as specified in the documentation at https://ignishpc.readthedocs.io/en/latest/started.html.

I have tested these images with ppc64le, and they worked without any issues. By examining the arguments for "ignis-deploy images build," you'll find that it's even possible to select the specific architecture you want to compile for.

Edit:
Regarding the operating system, you can use any OS that supports Docker or Singularity. In the case of Windows, it will need to be within the WSL2 (Windows Subsystem for Linux 2). You can find more information about this setup in the following link: https://docs.docker.com/desktop/wsl/.

[droeatpm]

Thank you. I'll try that advice and report back.

[droeatpm]

Can you help me with a problem with "ignis-deploy images build", or is there a better place for me to ask?
When I run this on a M2 mac
ignis-deploy images build --full --sources https://github.com/ignishpc/dockerfiles.git https://github.com/ignishpc/backend.git https://github.com/ignishpc/core-cpp.git https://github.com/ignishpc/core-python.git https://github.com/ignishpc/core-go.git

I get this

Build:
ignishpc/base:latest SUCCESS
ignishpc/zookeeper:latest SUCCESS
ignishpc/nomad:latest FAILED, check /Users/daver/bin/ignisbuild-nomad.log
ignishpc/mesos-base:latest FAILED, check /Users/daver/bin/ignisbuild-mesos-base.log
ignishpc/singularityce:latest SUCCESS
ignishpc/builder:latest SUCCESS
Aborting
RuntimeError: The command '/bin/sh -c mkdir /tmp/mesos && mkdir /tmp/root && cd /tmp/mesos && wget www.apache.org/dist/mesos/${_MESOS_VERSION}/mesos-${_MESOS_VERSION}.tar.gz && tar -zxf mesos-${_MESOS_VERSION}.tar.gz && cd mesos-${_MESOS_VERSION} && ./configure && make -j4 && make install DESTDIR=/tmp/root && rm -fR /tmp/mesos' returned a non-zero code: 1
ignisbuild-mesos-base.log
ignisbuild-nomad.log

Attached are the mesos and nomad logs.
ignisbuild-mesos-base.log
ignisbuild-nomad.log

[cesarpomar]

I recommend you to use "--ignore mesos nomad zookeeper" those modules are not necessary in your case and it is better to ignore them (take a long time to compile). I guess the ARM versions of mesos and nomad require changes in the installation process. I note that they need to be reviewed. Thanks

If you are only going to use Bigseqkit, you only need core-go, you can remove the core-cpp and core-python repos, it will compile faster and the images will be smaller.

[droeatpm]

When I get to ignis-deploy registry start --default, I get

info: darwin selected for internal cluster communications, use --bind to select another
APIError: 400 Client Error for http+docker://localhost/v1.43/containers/create?name=ignis-registry: Bad Request ("invalid mount config for type "bind": stat /host_mnt/private/var/lib/ignis/registry: permission denied")

Using ignis-deploy 2.2.1

[cesarpomar]

You can avoid this step because if you only use your laptop, you don't need a registry to share images with another computer. In any case, the registry tries to use a location where you don't have sufficient permissions. In Linux, Docker runs with root privileges, but on Mac with the hypervisor, I'm not sure.