summaryrefslogtreecommitdiff
path: root/contrib/spec/podman.spec.in
diff options
context:
space:
mode:
authorDaniel J Walsh <dwalsh@redhat.com>2020-06-19 06:41:58 -0400
committerDaniel J Walsh <dwalsh@redhat.com>2020-06-20 06:20:46 -0400
commit5b3503c0a1bf93dc327145e8952ed5b05932dee5 (patch)
tree1b8c4f54f14d6eb8079d7bf4a5b5fa2f81767ce1 /contrib/spec/podman.spec.in
parentf403aa3baa23a64e7d6bf3fcbc815644d95b768d (diff)
downloadpodman-5b3503c0a1bf93dc327145e8952ed5b05932dee5.tar.gz
podman-5b3503c0a1bf93dc327145e8952ed5b05932dee5.tar.bz2
podman-5b3503c0a1bf93dc327145e8952ed5b05932dee5.zip
Add container name to the /etc/hosts within the container
This will allow containers that connect to the network namespace be able to use the container name directly. For example you can do something like podman run -ti --name foobar fedora ping foobar While we can do this with hostname now, this seems more natural. Also if another container connects on the network to this container it can do podman run --network container:foobar fedora ping foobar And connect to the original container,without having to discover the name. Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
Diffstat (limited to 'contrib/spec/podman.spec.in')
0 files changed, 0 insertions, 0 deletions