You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mesos.apache.org by Marc Roos <M....@f1-outsourcing.eu> on 2019/07/21 00:24:51 UTC
Cant get sandbox_path to work
Don't know how to apply this manual correctly to map a image folder to
the sandbox.
http://mesos.apache.org/documentation/latest/container-volume/#sandbox_path-volume-source
{
"id": "/test2",
"user": "nobody",
"cpus": 1,
"mem": 256,
"disk": 0,
"instances": 1,
"acceptedResourceRoles": ["*"],
"backoffSeconds": 10,
"networks": [
{ "mode": "container", "name": "cni" }
],
"container": {
"type": "MESOS",
"docker": {
"image": "test",
"credential": null,
"forcePullImage": true
},
"volumes": [
{
"mode": "RW",
"container_path": "/usr/local/tomcat/logs",
"source": {
"type": "SANDBOX_PATH",
"sandbox_path": {
"type": "SELF",
"path": "tmp"
}
}
}
]
}
}
Re: [mesos-mail] Cant get sandbox_path to work
Posted by Gilbert Song <gi...@apache.org>.
Are you using Marathon?
The Mesos SANDBOX_PATH volume was supported by Marathon as the pod's
ephemeral volume. Please note that Mesos framework API is different from
Marathon API and refer to Marathon documentation if necessary.
-Gilbert
On Sat, Jul 20, 2019 at 5:25 PM Marc Roos <M....@f1-outsourcing.eu> wrote:
>
> Don't know how to apply this manual correctly to map a image folder to
> the sandbox.
>
> http://mesos.apache.org/documentation/latest/container-volume/#sandbox_path-volume-source
>
> {
> "id": "/test2",
> "user": "nobody",
> "cpus": 1,
> "mem": 256,
> "disk": 0,
> "instances": 1,
> "acceptedResourceRoles": ["*"],
> "backoffSeconds": 10,
> "networks": [
> { "mode": "container", "name": "cni" }
> ],
> "container": {
> "type": "MESOS",
> "docker": {
> "image": "test",
> "credential": null,
> "forcePullImage": true
> },
> "volumes": [
> {
> "mode": "RW",
> "container_path": "/usr/local/tomcat/logs",
> "source": {
> "type": "SANDBOX_PATH",
> "sandbox_path": {
> "type": "SELF",
> "path": "tmp"
> }
> }
> }
> ]
> }
> }
>
>