[
https://issues.apache.org/jira/browse/MESOS-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16013018#comment-16013018
]
John Kordich commented on MESOS-7407:
-------------------------------------
Confirming that I have encountered this as well, with similar error messages:
E0516 11:45:23.131611 19864 default_executor.cpp:468] Received '500 Internal
Server Error' (Failed to create nested sandbox directory
'C:\Users\JOHNKO~1.RED\AppData\Local\Temp\jEiLUX\slaves\53282974-b770-413f-b324-781b9efaf341-S0\frameworks\53282974-b770-413f-b324-781b9efaf341-0000\executors\default\runs\c8a2c2ca-5c09-4732-9c82-ed54c8d47d32\containers\a7845cfc-9690-41d7-a80e-85c91ca6b7f8':
No such file or directory) while launching child container
> Windows 10 Creators Update broke opt-in NTFS long path support
> --------------------------------------------------------------
>
> Key: MESOS-7407
> URL: https://issues.apache.org/jira/browse/MESOS-7407
> Project: Mesos
> Issue Type: Bug
> Components: agent
> Environment: Windows 10 with "Creators Update" (Build 15063)
> Reporter: Andrew Schwartzmeyer
> Assignee: Andrew Schwartzmeyer
> Labels: windows
>
> The Creators Update _seems_ to have broken the notion of opting into NTFS
> long path support (i.e. by setting a registry key or group policy). I've
> verified this on both my work and home desktops, which updated to the
> Creators Update, and subsequently the DefaultExecutorTests started to fail
> with "path is too long".
> I would appreciate other verification.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
