[ https://issues.apache.org/jira/browse/MESOS-7605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083358#comment-16083358 ]
James Peach commented on MESOS-7605: ------------------------------------ Assigning to me. What I would like to do here is simply enter a UTS namespace when using host networking. If the task is using a container image then we can probably support setting the hostname and updating the relevant config files as well. > UCR doesn't isolate uts namespace w/ host networking > ---------------------------------------------------- > > Key: MESOS-7605 > URL: https://issues.apache.org/jira/browse/MESOS-7605 > Project: Mesos > Issue Type: Improvement > Components: containerization > Reporter: James DeFelice > Assignee: James Peach > Labels: mesosphere > > Docker's {{run}} command supports a {{--hostname}} parameter which impacts > container isolation, even in {{host}} network mode: (via > https://docs.docker.com/engine/reference/run/) > {quote} > Even in host network mode a container has its own UTS namespace by default. > As such --hostname is allowed in host network mode and will only change the > hostname inside the container. Similar to --hostname, the --add-host, --dns, > --dns-search, and --dns-option options can be used in host network mode. > {quote} > I see no evidence that UCR offers a similar isolation capability. > Related: the {{ContainerInfo}} protobuf has a {{hostname}} field which was > initially added to support the Docker containerizer's use of the > {{--hostname}} Docker {{run}} flag. -- This message was sent by Atlassian JIRA (v6.4.14#64029)