For what it's worth, I've seen the same or similar behavior with Java processes (Jenkins build slave) under LX (latest platform as of last week) without any Docker involvement. In the end I didn't do the full tracing to debug it - I moved it to KVM instead. But the base behavior of the Jenkins slave process just suddenly exiting very soon after running a git command, with no error message in sight anywhere, was very reproducible.
//jb 2016-04-12 12:06 GMT+02:00 Nigel Magnay <[email protected]>: > Ok - I can successfully recreate this on the public cloud - I'll send you > some details separately. > > On Mon, Apr 11, 2016 at 9:08 PM, Nigel Magnay <[email protected]> > wrote: > >> Sure - I'm going to try and get a test container up on the Joyent cloud >> to at least see if it does the same thing there. >> >> Interestingly, it looks like it's timing related. If I attach a java >> debugger to a debug socket when running the build, it doesn't seem to fail. >> >> >> On Mon, Apr 11, 2016 at 8:28 PM, Elijah Zupancic <[email protected]> >> wrote: >> >>> Hi Nigel, >>> >>> I'm trying to verify this bug. I wasn't able to get your Dockerfile to >>> build because it was missing associated files. Is there a way for you to >>> build the Docker image and push it to Docker hub? If so, could you then try >>> to distill the repro steps down to a single command that I can execute >>> using docker exec? >>> >>> Thanks, >>> Elijah >>> ... >>> >> ------------------------------------------- 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
