This causes a side-effect for us where our logging program which is file
path based, has a hard time matching up stderr / stdout and other logs to
the applications that are generating them. I've been meaning to write a
https://mesos.apache.org/documentation/latest/logging/ ContainerLogger that
can
The problem referred in the ticket does not exist any more. We now use
Mesos generated container ID as the cgroup path (since 0.18?).
That reminds me that the nested container ID might have this restriction
because it's generated by the executor. We should add a validation in the
agent.
- Jie
Dear Mesos developers and users,
Please vote on releasing the following candidate as Apache Mesos 1.2.0.
1.2.0 includes the following:
* [MESOS-5931] - **Experimental** Support auto backend in Mesos
Containerizer,
