mesos-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marc Roos" <M.R...@f1-outsourcing.eu>
Subject RE: Container user '27' is not supported
Date Mon, 25 Dec 2017 22:22:46 GMT
 
Should this be done via the parameters? What key?

"parameters": [{ "key": "net", "value": "host" }]


{
  "id": "sflow/vizceral",
  "cmd": null,
  "cpus": 0.2,
  "mem": 256,
  "instances": 1,
  "acceptedResourceRoles": ["*"],
  "constraints": [["hostname", "CLUSTER", "m02.local"]],
  "container": {
    "type": "MESOS",
    "docker": {
      "image": "sflow/vizceral",
      "credential": null,
      "forcePullImage": false
    }

  }
}


Dec 25 23:15:40 m02 mesos-slave[18569]: W1225 23:15:40.251715 18595 
runtime.cpp:111] Container user 'sflowrt' is not supported yet for 
container 375b21ca-2d12-4a81-8429-897aac75eaa0
Dec 25 23:15:40 m02 mesos-slave[18569]: W1225 23:15:40.251715 18595 
runtime.cpp:111] Container user 'sflowrt' is not supported yet for 
container 375b21ca-2d12-4a81-8429-897aac75eaa0

-----Original Message-----
From: James Peach [mailto:jorgar@gmail.com] 
Sent: zondag 24 december 2017 18:01
To: user
Subject: Re: Container user '27' is not supported



> On Dec 24, 2017, at 5:20 AM, Marc Roos <M.Roos@f1-outsourcing.eu> 
wrote:
> 
> 
> I am seeing this in the logs:
> 
> Container user '27' is not supported yet for container
> d823196a-4ec3-41e3-a4c0-6680ba5cc99
> 
> I guess this means that the container requests to run under a specific 

> user id, and this is not yet available in mesos?

This means that the containerizer parsed the continaer user out of the 
manifest, but we don’t support running the container as that user. You 
should continue to use the TaskInfo message to specify which user the 
container will run as.

J


Mime
View raw message