waiting the mesos containerizer become maturity.
2016-11-07 8:57 GMT+08:00 Tobias Pfeiffer :
> Hi,
>
> thanks to both of you for your reply. For the moment I switched to using
> a Mesos container without an underlying Docker image, and then execute
> `docker run myimage ` in that container. I g
Hi,
thanks to both of you for your reply. For the moment I switched to using a
Mesos container without an underlying Docker image, and then execute
`docker run myimage ` in that container. I guess there will be a
number of issues with that approach at some point, but for the moment it is
ok.
Th
To add to haosdent's reply:
- I have a USER directive in my Dockerfile in order for the CMD to be
> executed as that user, but that does not seem to be supported (yet?) by the
> Docker image provider. Is there any method (except `sudo`/`setuser`) to
> achieve running as a user present in the image
>- Is it possible to hide host processes from the container?
You may consider to use the namespaces/pid isolator, add `namespaces/pid`
in the `--isolation` flag when launch Mesos Agent
> -Is it possible to run processes that open network ports (possibly
already open on the host system) and have the
Actually, say I was in a fancy mood, could I actually *not* use the Docker
image provider and instead run `nvidia-docker run [more hand-crafted
parameters] myimage ` as an ordinary command within the Mesos
container, or would I have to dig very deep into Mesos to find the right
parameters to pass t
Hi,
I asked this question also yesterday in the #mesos channel on IRC, but I
guess due to timezone differences there were not many people awake and/or
working, sorry for reposting. (Maybe someone answered after I left, but it
seems that the IRC bot is only archiving channel joins/leaves? ->
http:/
6 matches
Mail list logo
