I'll dig out the Dockerfile on monday - it's not particularly complex. Basically the (jenkins) build process asks triton to instantiate a (java:8) docker image, the uses ssh to connect and invoke maven. I can connect 'by hand' and also make it die - though it may be that it's only doing this on some nodes.
The most likely explanation is I've either misunderstood or misconfigured something. There would seem to be enough free memory and swap on the host whilst it's running, but might there be other limits (processes?) that may have been breached causing it to be killed? On Fri, Apr 8, 2016 at 10:20 PM, Elijah Zupancic <[email protected]> wrote: > Hi Nigel, > > Could you please give us some additional information. Could you tell us > the platform image version. You can find it by doing a uname -a or if you > are within a docker container a /native/bin/uname -a > > Also, with regards to the Docker build process are you using Docker build > with Triton or are you using Docker build with Linux Docker and then > running the built image on Triton? > > Also, if you Dockerfile isn't sensitive could you please share it with us? > I can attempt to reproduce. Another way to narrow down problems is to try > to run it in the Joyent public cloud and to see if it dies there. > > Thanks, > Elijah > > On Fri, Apr 8, 2016 at 6:11 AM, Nigel Magnay <[email protected]> > wrote: > >> Hi - >> >> I've successfully built a Triton cloud, and am using it to provision >> docker containers to build our java software. >> >> The java container I use is derived from "java:8" docker image. >> >> Mostly it works. However I am getting mysterious failures where the build >> process (maven) simply exits half way through with no error. I have a test >> system that is spun up that, mostly, consistently fails in the same place. >> >> dmesg from inside the container yields nothing. Irritatinly, if I do >> 'strace -ff -o me ...', the build continues past the point it was failing. >> If I try to monitor the process from a second connection - sometimes the >> build continues and *that* connection just dies. >> >> I was able to connect briefly with truss from the GZ, but I'm not sure it >> tells me very much. >> >> >> Could I have hit some process accounting limit? I don't think it's memory >> (the process is set to a fairly low java Xmx limit). Where else can I look >> to figure this out? >> >> > > > -- > -Elijah > *smartos-discuss* | Archives > <https://www.listbox.com/member/archive/184463/=now> > <https://www.listbox.com/member/archive/rss/184463/22541698-24d6dc34> | > Modify > <https://www.listbox.com/member/?&;> > Your Subscription <http://www.listbox.com> > ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
