Hi Neale, Linux on 390 Port <[email protected]> wrote on 24.03.2015 19:03:33: > Trying to run docker to do a build with docker started with -d, I get a > SEGV doing a lookup of registry-1.docker.io:
we have been observing this, too, and are in the process of verifying a new build. I noticed these issues when using tags other than latest, and then forgetting to specify a tag when referring to an image (so you have neales-image:v1, but no neales-image:latest -- it crashes when referring to just neales-image). Docker will try to find the image someplace else, and then the address resolution fails. This is caused by our statically linking glibc, which collides with the go runtime environment. The solution we are pursueing dynamically links against glibc (and some other libraries). As soon as we've given it some test runs, we'll upload it (matter of days) and I'll send a quick mail. One thing, though: Dockerfiles and everything works, however you have to refer to an s390x base image, so depending on ubuntu 14.04 on the Docker hub won't work. To get lean base images, check out http://containerz.blogspot.co.uk/2015/03/creating-base-images.html . Thanks, Utz :wq ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
