[jira] [Created] (MESOS-7105) Start Mesos Agent even if CNI dir doesn't exist

["Dan Osborne (JIRA)" <ji...@apache.org>]

Dan Osborne created MESOS-7105:
----------------------------------

             Summary: Start Mesos Agent even if CNI dir doesn't exist
                 Key: MESOS-7105
                 URL: https://issues.apache.org/jira/browse/MESOS-7105
             Project: Mesos
          Issue Type: Improvement
            Reporter: Dan Osborne
            Assignee: Avinash Sridharan


Mesos-agent refuses to start if a CNI config directory has been configured but does not exist. I propose that we don't bother to check this at start.

Now that Mesos scans for CNI configs at task launch, it's feasible that even though the directory doesn't exist at launch, it will be filled with configs by the time the a task is run.

Specifically, for my use case, I'm trying to install CNI plugins using the Docker Containerizer in Mesos. These tasks volume mount in the CNI directories which the docker daemon automatically creates if they don't exist. But I can't get the slave to start unless I make the CNI conf dir, which feels unnecessary.

{code}
Failed to create a containerizer: Could not create MesosContainerizer: Failed to create isolator 'network/cni': The CNI network configuration directory '/etc/cni/net.d/' does not exist
{code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)