Kevin Klues created MESOS-6954:
----------------------------------
Summary: Running LAUNCH_NESTED_CONTAINER with a docker container
id crashes the agent
Key: MESOS-6954
URL: https://issues.apache.org/jira/browse/MESOS-6954
Project: Mesos
Issue Type: Bug
Reporter: Kevin Klues
Priority: Blocker
Attempting to run {{LAUNCH_NESTED_CONTAINER}} with a parent container that was
launched with the docker containerizer causes the agent to crash as below. We
should add a safeguard in the handler to fail gracefully instead.
{noformat}
I0119 21:41:42.438295 3281 http.cpp:304] HTTP POST for /slave(1)/api/v1 from
10.0.7.194:46700 with User-Agent='python-requests/2.12.4' with
X-Forwarded-For='10.0.6.162'
I0119 21:41:42.441571 3281 http.cpp:465] Processing call
LAUNCH_NESTED_CONTAINER_SESSION
W0119 21:41:42.442286 3281 http.cpp:2251] Failed to launch nested container
62a16556-9c3b-48f2-aa1e-ba1d70093637.09a9d3b0-a245-4aa1-94f1-d10a13526b9b:
Unsupported
F0119 21:41:42.442371 3282 docker.cpp:2013] Check failed:
!containerId.has_parent()
*** Check failure stack trace: ***
@ 0x7f539aca01ad google::LogMessage::Fail()
@ 0x7f539aca1fdd google::LogMessage::SendToLog()
@ 0x7f539ac9fd9c google::LogMessage::Flush()
@ 0x7f539aca28d9 google::LogMessageFatal::~LogMessageFatal()
@ 0x7f539a46e2cd
mesos::internal::slave::DockerContainerizerProcess::destroy()
@ 0x7f539a48a8a7
_ZNSt17_Function_handlerIFvPN7process11ProcessBaseEEZNS0_8dispatchIbN5mesos8internal5slave26DockerContainerizerProcessERKNS5_11ContainerIDEbS9_bEENS0_6FutureIT_EERKNS0_3PIDIT0_EEMSG_FSE_T1_T2_ET3_T4_EUlS2_E_E9_M_invokeERKSt9_Any_dataS2_
@ 0x7f539ac14ca1 process::ProcessManager::resume()
@ 0x7f539ac1dba7
_ZNSt6thread5_ImplISt12_Bind_simpleIFZN7process14ProcessManager12init_threadsEvEUt_vEEE6_M_runEv
@ 0x7f53990a5d73 (unknown)
@ 0x7f5398ba652c (unknown)
@ 0x7f53988e41dd (unknown)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
