Cannot run this image on zLinux

[Equalampion]

Here is the docker events after we issue 'docker run -it s390x/ubuntu /bin/bash'

2017-01-05T04:03:51.498465000-08:00 container resize abaa376026d1145bfae2ae81715b813a14c450478c963d1d17b765ebbd6a2f53 (height=45, image=s390x/ubuntu, name=loving_liskov, width=168)
2017-01-05T04:03:51.783611000-08:00 container die abaa376026d1145bfae2ae81715b813a14c450478c963d1d17b765ebbd6a2f53 (exitCode=132, image=s390x/ubuntu, name=loving_liskov)
2017-01-05T04:03:52.391217000-08:00 network disconnect fcad39f1a56957b559f2500b1c36c9551b2c7f12c77038ef5e411db2d385f082 (container=abaa376026d1145bfae2ae81715b813a14c450478c963d1d17b765ebbd6a2f53, name=bridge, type=bridge)

What is (exitCode=132, exactly? Can we have more detail about this ? Which action is triggering this problem?

Thank you!

[tianon]

Is your s390x machine's arch supported by Ubuntu? IIRC, they don't support z10, for example (even though Debian does).

[Equalampion]

Actually, this is based on z/VM....Still confirming if it is z10.

[Equalampion]

Confirmed that they are zLinux by z/VM based on z196. Is it supported?

[Equalampion]

Thank you very much for the help. Is exit code 132 an auth problem? Do you know what is the trigger of that?

[tianon]

Yeah, z196 should be supported. 😕

I'm not sure what exit code 132 is -- it shouldn't be an auth problem, since it's coming from the container process (not Docker or the Hub). I think it might still be SIGILL, which lends credence to the theory that the processor isn't supported by Ubuntu's compiled binaries. You mentioned this is a VM? Is the VM's CPU still z196, or is it older than that? Usually, SIGILL happens when a binary contains an instruction the system's CPU cannot understand (I had the same problem while building the Ubuntu images until I got access to a newer s390x system).

[Equalampion]

I am not expert of z/VM. But basically, the CPU this zLinux using is simulated from actual z196 CPU in this box. But after simulation through z/VM, I am not quite sure if Docker can still map to the correct CPU structure or something....

[Equalampion]

Or....is that any other way that we an find more detail information to find out what happened exactly? Those exit code 132 is from 'docker events' command...any other debug way? Thank you very much for your help.

[Equalampion]

We tried two real zLinux machine, this image can be run on them without exit code 132. But in zLinux on z/VM, another two zlinux failed to run this exactly same image.