Set hostname inside docker box

[kim0]

As a puppet user, I should be able to set the hostname inside the docker (box?) as seen by processes running inside it. I use hostnames to set puppet roles, thus this is quite important in my use case

Thanks

[jpetazzo]

That should work already, thanks to the uts namespace.

Can you please describe what you were trying to do, what you were expecting, and what happened?

Thank you!

[shykes]

@kim0 would this be a good solution for you?

docker run -h MY_HOSTNAME /bin/sh -c 'my hostname is $(hostname)'

[kim0]

Yes absolutely, I didn't look hard enough. Thanks folks

On Fri, Mar 29, 2013 at 3:13 AM, Solomon Hykes notifications@github.comwrote:

@kim0 https://github.com/kim0 would this be a good solution for you?

docker run -h MY_HOSTNAME /bin/sh -c 'my hostname is $(hostname)'

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/243#issuecomment-15624414
.

[progrium]

Perhaps this should be tied to container naming.

On Thu, Mar 28, 2013 at 6:29 PM, kim0 notifications@github.com wrote:

Yes absolutely, I didn't look hard enough. Thanks folks

On Fri, Mar 29, 2013 at 3:13 AM, Solomon Hykes notifications@github.comwrote:

@kim0 https://github.com/kim0 would this be a good solution for you?

docker run -h MY_HOSTNAME /bin/sh -c 'my hostname is $(hostname)'

—
Reply to this email directly or view it on GitHub<
https://github.com/dotcloud/docker/issues/243#issuecomment-15624414>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/243#issuecomment-15624809
.

Jeff Lindsay
http://progrium.com

[shykes]

See #299

[progrium]

It would be rad if you could then refer to containers by hostname instead
of ID. :D

On Mon, Apr 1, 2013 at 2:43 PM, Solomon Hykes notifications@github.comwrote:

See #299 #299

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/243#issuecomment-15739222
.

Jeff Lindsay
http://progrium.com

[sa2ajj]

@progrium, maybe you could open another issue and describe the scenario you envision?

My personal feeling is that referring to the container by the host name might be ambigous in certain scenarios...

[progrium]

That would really be up to you to make it ambiguous. You can always fall
back to ID. Anywhere you use ID, you should be able to use hostname. Or
some other alias. But since we have custom hostnames, we might as well use
that for naming?

On Mon, Apr 1, 2013 at 2:52 PM, Mikhail Sobolev notifications@github.comwrote:

@progrium https://github.com/progrium, maybe you could open another
issue and describe the scenario you envision?

My personal feeling is that referring to the container by the host name
might be ambigous in certain scenarios...

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/243#issuecomment-15739655
.

Jeff Lindsay
http://progrium.com

[danmayer]

is there a reason this strips out anything with subdomains?

kr@utils:~/dockerfiles/graphite$ docker run -h 'utils.mysite.com' -i -t ubuntu /bin/bash
root@utils:/# echo $(hostname)
utils

[ghost]

It sets the host and domain names:

$ docker run -h foo.bar.baz -i -t ubuntu bash
root@foo:/# hostname
foo
root@foo:/# hostname -d
bar.baz
root@foo:/# hostname -f
foo.bar.baz
root@foo:/#

[danmayer]

Awesome thanks a bunch, learning new things I am sure that was a pretty obvious fail on my part. ;)