boinc docker exits immediately after running command (s390x z/OS suse)

Question

boinc docker exits immediately after running command (s390x z/OS suse)

sunk818 opened this issue 6 years ago · 18 comments

I ran the following command on s390x architecture (IBM z/OS) mainframe using SUSE:

docker run -d \
  --name boinc \
  --net=host \
  -v /opt/appdata/boinc:/var/lib/boinc-client \
  -e BOINC_GUI_RPC_PASSWORD="123" \
  -e BOINC_CMD_LINE_OPTIONS="--allow_remote_gui_rpc" \
  boinc/client

~> sudo docker ps -a
CONTAINER ID        IMAGE               COMMAND                 CREATED             STATUS                    PORTS               NAMES
5df225cbc86b        boinc/client        "start-boinc.sh"        17 hours ago        Exited (1) 17 hours ago                       laughing_visvesvaraya

:~> sudo docker logs 5df225cbc86b
standard_init_linux.go:185: exec user process caused "exec format error"

Does this mean the docker image is not compatible with the s390x architecture?

~> uname -a
Linux linux1-marist-03 4.4.103-94.6-default #1 SMP Tue Jan 9 12:53:49 UTC 2018 (69ac2b4) s390x s390x s390x GNU/Linux

:~> cat /etc/os-release
NAME="SLES"
VERSION="12-SP3"
VERSION_ID="12.3"
PRETTY_NAME="SUSE Linux Enterprise Server 12 SP3"
ID="sles"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:suse:sles:12:sp3"

Answer 1 · 2018-10-17T20:29:00.000Z

The issue must be with the s390x architecture. I created a new image for you. When it's compiled, I'll let you know the details.

Answer 2 · 2018-10-17T20:58:42.000Z

Currently I can't even run the standard s390x Ubuntu image on my system.
The command I tried: sudo docker run -ti s390x/ubuntu:18.04 bash
The error message I got: standard_init_linux.go:190: exec user process caused "exec format error"

Answer 3 · 2018-10-17T21:05:31.000Z

Thank you for trying. I know this is rare architecture to work with s390x and even the OS (enterprise) is not so common like RHEL Linux.

Does Docker care what kind of line ending is used? For example, Windows hex is 0D0A while Unix is 0A for line endings. Second article mentions XML may not be processed correctly depending on how line endings are processed?

Is this helpful? https://www.lewuathe.com/exec-format-error-in-docker-container.html
or https://blog.hompus.nl/2018/01/24/docker-run-throws-exec-user-process-errors/

Answer 4 · 2018-10-17T21:19:08.000Z

Could you try building the image on your system.
Here is the command:
docker build -t boinc/client:s390x -f Dockerfile.s390x .

Answer 5 · 2018-10-18T01:02:49.000Z

Attached is the output. I did a git pull then ran the command you asked.

I am not sure if the docker container rebuilt correctly. I got the same error when I checked the logs of the docker container.

boinc-docker-s390x.log

Answer 6 · 2018-10-18T06:00:13.000Z

It looks the container built correctly.
Did you use the built image, with the s390x tag?

docker run -d \
  --name boinc \
  --net=host \
  -v /opt/appdata/boinc:/var/lib/boinc-client \
  -e BOINC_GUI_RPC_PASSWORD="123" \
  -e BOINC_CMD_LINE_OPTIONS="--allow_remote_gui_rpc" \
  boinc/client:s390x

Answer 7 · 2018-10-18T08:58:19.000Z

The main question is, there will be any project that support your architecture?

Answer 8 · 2018-10-20T03:33:32.000Z

Hi, your suggestion solved it.

Ran into some issue with xorg:x11 docker boinc looking for /var/input/mice (?), but otherwise seemed to work until

I tried with Rosetta@Home, World Community Grid, Collatz Conjecture, and SETI@Home. None support s390x architecture.

Answer 9 · 2018-10-20T06:55:02.000Z

The /var/input/mice issue is solved in a the newer version.
Then I remove this image until no one support it. Maybe you should write for the Seti@H, if any chance to build the project to you platform. I see the biggest chance with them.

Answer 10 · 2018-10-21T08:19:38.000Z

@davidpanderson Do you see any chance to build a project that run on s390x architecture?

Answer 11 · 2018-10-23T09:08:24.000Z

s390x is an IBM mainframe architecture?
Do you mean to use it as a BOINC server or as a client?
Do any of them exist?

Answer 12 · 2018-10-23T09:19:10.000Z

@davidpanderson We were able to build the boinc client for the s390x architecture, but there is no project that support it so he can't crunch the WUs. Do you see any chance that S@H can support it in the near future?

Answer 13 · 2018-10-25T05:45:36.000Z

If someone builds and tests the S@h client for s390x, Eric Korpela might release it. Or you could run it using anonymous platform.

Answer 14 · 2018-10-25T15:09:05.000Z

@sunk818 what do you think, do you wanna give a try?

Answer 15 · 2018-10-28T04:49:34.000Z

@adamradocz I'm happy to do it if you provide me the steps. s390x platform using SUSE Linux. I don't have entitlement for Red Hat 7, so I'm not allowed to use it.

Answer 16 · 2018-10-28T05:55:11.000Z

Honesty,I have no idea how to do that. Maybe @davidpanderson can give you some guidance.

Answer 17 · 2018-10-28T06:13:09.000Z

It's described here:
https://boinc.berkeley.edu/wiki/Anonymous_platform
The idea is that you get the source code of the app (S@h in this case),
build it and link it with the BOINC runtime library,
and make a config file that tells the server to use your app.

-- David

Answer 18 · 2018-10-29T20:36:48.000Z

I close this issue. @sunk818 if you succeed with building the project, I will recreate the s390x image.