On 4/22/16 8:48 , Elijah Zupancic wrote: > Hi Danny, > > The fix is included in the latest platform image available from the dev > channel.
Channels are an SDC-ism so if you're just running straight up SmartOS, this may be a bit confusing. In this case, the fix will be in the upcoming release on April 28th. There are nightly builds available though in manta if that's something you're interested in. Robert > On Apr 22, 2016 8:45 AM, "Danny Wilson" <[email protected]> wrote: > >> That's great to hear, I'm experiencing this issue as well. >> >> Is there an updated SmartOS build I could try? :-) >> >> >> On Mon, Apr 18, 2016, at 06:06 PM, Elijah Zupancic wrote: >> >> This issue has now been fixed and checked in. If you are interested the >> details are here: https://smartos.org/bugview/OS-5323 >> >> On Wed, Apr 13, 2016 at 12:23 AM, Jakob Borg <[email protected]> wrote: >> >> 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 >> >> ... >> >> >> >> >> -- >> -Elijah >> *smartos-discuss* | Archives >> <https://www.listbox.com/member/archive/184463/=now> >> <https://www.listbox.com/member/archive/rss/184463/27824080-914e3e6d> | >> Modify <https://www.listbox.com/member/?&;> Your Subscription >> <http://www.listbox.com> >> >> >> *smartos-discuss* | Archives >> <https://www.listbox.com/member/archive/184463/=now> >> <https://www.listbox.com/member/archive/rss/184463/27862676-268a510e> | >> 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
